Triple
T181189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Manchester City Council |
E3879
|
entity |
| Predicate | featuresCharge |
P6310
|
FINISHED |
| Object | red shield |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: red shield | Statement: [Coat of arms of Manchester City Council, featuresCharge, red shield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresCharge Context triple: [Coat of arms of Manchester City Council, featuresCharge, red shield]
-
A.
charge
Indicates that one entity formally accuses another of an offense or imposes a financial cost or obligation on them.
-
B.
chargeOftenUsed
Indicates that an entity is frequently subjected to or associated with a particular charge (such as a legal, financial, or electrical charge).
-
C.
featuresText
Indicates that an entity includes or presents a specific piece of text as one of its characteristics or contents.
-
D.
legalCharge
Indicates that an authority has formally accused an entity of committing a specific legal offense or violation.
-
E.
hasElectricCharge
Indicates that an entity possesses a nonzero electric charge as a physical property.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25923507c8190bd7f6eda404b0da0 |
completed | Feb. 28, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69a2566ccc288190add5624ede96d82b |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2575e7c7c819095167d8a862c255a |
completed | Feb. 28, 2026, 2:47 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.