Triple
T1078200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Water Level Route |
E23885
|
entity |
| Predicate | constructionCharacteristic |
P23657
|
FINISHED |
| Object | avoids steep grades |
—
|
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: avoids steep grades | Statement: [Water Level Route, constructionCharacteristic, avoids steep grades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionCharacteristic Context triple: [Water Level Route, constructionCharacteristic, avoids steep grades]
-
A.
constructionType
Indicates the specific method or style by which something is built or constructed.
-
B.
constructionMethod
Indicates the technique or process by which something is built, assembled, or created.
-
C.
architectureProperty
Indicates that a specified architectural characteristic or feature is attributed to, or associated with, an entity.
-
D.
buildingSection
Indicates a relationship where one entity is a specific section, part, or subdivision of a larger building.
-
E.
constructionLabor
Indicates a relationship where an entity performs or provides labor specifically for construction-related work or projects.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b94288d88190aae4fb86236c0702 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73ba8208190be7f3cef8c18689b |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b80f0fb08190a19a50e38ae8f16c |
completed | March 1, 2026, 10:05 p.m. |
Created at: March 1, 2026, 7:42 p.m.