Triple
T10889803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewry Wall |
E257143
|
entity |
| Predicate | previouslyMisidentifiedAs |
P49451
|
FINISHED |
| Object | Roman town gate |
—
|
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: Roman town gate | Statement: [Jewry Wall, previouslyMisidentifiedAs, Roman town gate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyMisidentifiedAs Context triple: [Jewry Wall, previouslyMisidentifiedAs, Roman town gate]
-
A.
misidentifiedAs
chosen
Indicates that one entity has been incorrectly recognized, labeled, or understood as another, distinct entity.
-
B.
previouslyMisattributedTo
Indicates that something was earlier, but incorrectly, attributed or credited to a particular entity before being reassigned correctly.
-
C.
reasonForMisidentification
Indicates the explanation or cause behind why one entity was incorrectly identified as another.
-
D.
formerSpecies
Indicates that an entity was previously classified as a particular species but no longer holds that species status.
-
E.
previouslyObserved
Indicates that the subject entity has been seen, recorded, or encountered at some earlier time prior to the current context.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d752041e2c8190b513dc9dc5857fcc |
completed | April 9, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.