Triple
T17053583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huancaya |
E413762
|
entity |
| Predicate | hasBuiltStructure |
P93817
|
FINISHED |
| Object | stone bridges |
—
|
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 bridges | Statement: [Huancaya, hasBuiltStructure, stone bridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuiltStructure Context triple: [Huancaya, hasBuiltStructure, stone bridges]
-
A.
hasBuilt
Indicates that one entity is the creator or constructor of another entity.
-
B.
builtStructureFor
Indicates that one entity constructed or assembled a structure specifically intended for the use, benefit, or purpose of another entity.
-
C.
hasBuildingForm
Indicates that an entity possesses or is characterized by a particular architectural or structural building form.
-
D.
hasBuildingFrom
Indicates a relationship where a location or site possesses or includes a building that originates from, or was constructed in, a specified time period, source, or context.
-
E.
structureTypeBuilt
chosen
Indicates the type or kind of structure that was constructed in a building or creation event.
- 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3daa491008190ad013ee37532aa51 |
completed | April 18, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:34 a.m.