Triple
T8197780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Staro-Kalinkin Bridge |
E191475
|
entity |
| Predicate | hasLoadBearingStructure |
P50946
|
FINISHED |
| Object | stone arches |
—
|
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: stone arches | Statement: [Staro-Kalinkin Bridge, hasLoadBearingStructure, stone arches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLoadBearingStructure Context triple: [Staro-Kalinkin Bridge, hasLoadBearingStructure, stone arches]
-
A.
hasHumanStructure
Indicates that one entity possesses or exhibits a structural form or organization characteristic of humans.
-
B.
isEngineeredStructure
Indicates that something is a man-made or artificially constructed structure, typically designed and built through engineering processes.
-
C.
hasBridgeOrStructure
Indicates that there exists a bridge or similar structural connection between the related entities.
-
D.
buildingStructure
chosen
Indicates that one entity is a structural component or physical part that forms, supports, or constitutes the construction of another entity.
-
E.
hasOverheadStructures
Indicates that one entity possesses or includes structural elements positioned above or spanning over another area or object.
- 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_69ca82c6e9548190a4c5ca14516e4417 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5c2341f881908be59c378896e5bc |
completed | March 31, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:42 p.m.