Triple
T4041068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Park River |
E83947
|
entity |
| Predicate | enclosedInConduits |
P53760
|
FINISHED |
| Object | mid-20th century |
—
|
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-20th century | Statement: [Park River, enclosedInConduits, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enclosedInConduits Context triple: [Park River, enclosedInConduits, mid-20th century]
-
A.
partOfTunnel
Indicates that one entity forms a physical segment or component within the structure or extent of a tunnel.
-
B.
hasConveyorBeltTo
Indicates that one location, machine, or area is connected to another by a conveyor belt that transports items between them.
-
C.
hasVentilationShafts
Indicates that one entity is equipped with or contains ventilation shafts that provide airflow or air passage.
-
D.
hasEnclosures
Indicates that an entity possesses or contains one or more enclosing structures, spaces, or bounded areas associated with it.
-
E.
requiresContinuousCableRun
Indicates that the relationship or action can only be fulfilled if there is an unbroken, end-to-end cable connection between the involved entities.
- 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_69aed92f7cf0819098e0539bdcc3767f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb3a9314819095dcf47675eedb48 |
completed | March 9, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69aef900386481909d04555a9ec9b0e3 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aef98ed84c81909dc86097df4afd4f |
completed | March 9, 2026, 4:47 p.m. |
Created at: March 9, 2026, 3:37 p.m.