Triple
T24154043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redheugh Bridge |
E598624
|
entity |
| Predicate | hasPreviousStructure |
P14623
|
FINISHED |
| Object | first Redheugh Bridge |
—
|
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: first Redheugh Bridge | Statement: [Redheugh Bridge, hasPreviousStructure, first Redheugh Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPreviousStructure Context triple: [Redheugh Bridge, hasPreviousStructure, first Redheugh Bridge]
-
A.
hasStructureHistory
Indicates that there exists a record or account detailing the past states, changes, or development of a structure over time.
-
B.
previousStructure
chosen
Indicates that one structure directly precedes another in a defined sequence or configuration.
-
C.
hasPredecessorStructureFrom
Indicates that one structure existed or was established before another structure in a sequential or developmental order.
-
D.
hasStructureAbove
Indicates that one entity has another entity positioned vertically higher or located on top of it within a structural or spatial arrangement.
-
E.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
- 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_69e288cb0a3081909ef221744f274384 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e0e2e83081908e543ef266a27ec9 |
completed | April 29, 2026, 10:43 a.m. |
| PD | Predicate disambiguation | batch_69f176585f3481909beb907de252cd98 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:31 p.m.