Triple
T6274530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Province of Lichfield |
E140622
|
entity |
| Predicate | lostMetropolitanStatus |
P62282
|
FINISHED |
| Object | 803 |
—
|
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: 803 | Statement: [Province of Lichfield, lostMetropolitanStatus, 803]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostMetropolitanStatus Context triple: [Province of Lichfield, lostMetropolitanStatus, 803]
-
A.
metropolitanStatusHeld
Indicates that an entity holds or is assigned a particular metropolitan status (e.g., being designated as part of a metropolitan area or category).
-
B.
lostStatus
chosen
Indicates that an entity has transitioned into a state of being lost, missing, or no longer in its expected or intended possession or location.
-
C.
hasMetropolitan
Indicates that an entity is associated with, served by, or located within a specific metropolitan area.
-
D.
lostIn
Indicates that an entity has become unable to find its way or is no longer in control or possession within a particular place, situation, or context.
-
E.
metropolitan
Indicates that a location is part of, belongs to, or lies within a specified metropolitan (urban) area.
- F. None of above.
Provenance (3 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_69c008cc158881908df6ec94a911c736 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063c0629c8190805ddf1a604e9ca4 |
completed | March 22, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69c05606fb50819082d1a5a91e5030b6 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:25 p.m.