Triple
T24141715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chain of Rocks Bridge |
E598252
|
entity |
| Predicate | isEngineeredWith |
P62261
|
FINISHED |
| Object | mid-river bend to avoid river navigation hazards |
—
|
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: mid-river bend to avoid river navigation hazards | Statement: [Chain of Rocks Bridge, isEngineeredWith, mid-river bend to avoid river navigation hazards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEngineeredWith Context triple: [Chain of Rocks Bridge, isEngineeredWith, mid-river bend to avoid river navigation hazards]
-
A.
engineeredForLabel
Indicates that something has been specifically designed, adapted, or optimized to serve, support, or be used for the referenced label or purpose.
-
B.
engineeredBy
Indicates that an entity has been designed, created, or developed through the technical work or expertise of another entity.
-
C.
badgeEngineeredFrom
Indicates that a badge is derived, created, or generated based on another underlying source, design, or system.
-
D.
isEngineeredStructure
chosen
Indicates that something is a man-made or artificially constructed structure, typically designed and built through engineering processes.
-
E.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
- 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e00737c08190af7c62d0aab30571 |
completed | April 29, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:28 p.m.