Triple
T20022255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Framwellgate Bridge |
E494891
|
entity |
| Predicate | isHistoricCrossing |
P138400
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Framwellgate Bridge, isHistoricCrossing, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricCrossing Context triple: [Framwellgate Bridge, isHistoricCrossing, true]
-
A.
isHistoric
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
-
B.
isHistoricCourseAt
Indicates that a course has historically been offered or held at a particular institution or location.
-
C.
isHistoricCourse
Indicates that a course has historical significance, typically due to its age, legacy, or notable past events associated with it.
-
D.
hasHistoricTerminal
Indicates that an entity possesses or is associated with a historically significant terminal facility or endpoint.
-
E.
isHistoricRegionFor
Indicates that one entity serves as a historically recognized region associated with, or significant to, another entity.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66288fc18819083833b55c5e069a6 |
completed | April 20, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:35 p.m.