Triple
T25973767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bootham Bar |
E645877
|
entity |
| Predicate | hasEarlierStructureOnSite |
P159860
|
FINISHED |
| Object | Roman gateway |
—
|
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 gateway | Statement: [Bootham Bar, hasEarlierStructureOnSite, Roman gateway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEarlierStructureOnSite Context triple: [Bootham Bar, hasEarlierStructureOnSite, Roman gateway]
-
A.
hasStructureOnOrAdjacent
Indicates that one entity has a physical structure located on it or immediately next to it.
-
B.
hasStructureAbove
Indicates that one entity has another entity positioned vertically higher or located on top of it within a structural or spatial arrangement.
-
C.
hasStructureHistory
Indicates that there exists a record or account detailing the past states, changes, or development of a structure over time.
-
D.
hasFormerBuilding
Indicates that an entity previously occupied or used a different building, which is identified as its former building.
-
E.
hasReconstructedSite
Indicates that an entity has a site or location that has been rebuilt or restored after damage, destruction, or alteration.
- 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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f60506b5ac8190a041db443a12e8a7 |
completed | May 2, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 22, 2026, 8:51 a.m.