Triple
T30363125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rendsburg High Bridge |
E772342
|
entity |
| Predicate | approachStructure |
P37520
|
FINISHED |
| Object | elevated loop viaduct |
—
|
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: elevated loop viaduct | Statement: [Rendsburg High Bridge, approachStructure, elevated loop viaduct]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approachStructure Context triple: [Rendsburg High Bridge, approachStructure, elevated loop viaduct]
-
A.
approachStructureType
Indicates that one entity moves closer to or advances toward a specified type of structure.
-
B.
hasApproachStructure
chosen
Indicates that one entity possesses or includes an approach structure that provides access or a path leading to another entity.
-
C.
viaStructure
Indicates that one entity is connected to or accessed through a particular structural element or medium.
-
D.
exploresStructureOf
Indicates a relationship where one entity investigates, analyzes, or examines the organization, composition, or arrangement of another entity.
-
E.
proposedStructure
Indicates that one entity has suggested or put forward another entity as a potential structure or structural arrangement.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: April 29, 2026, 7:58 p.m.