Triple
T20513259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tambomachay |
E503615
|
entity |
| Predicate | hasHydraulicEngineering |
P105596
|
FINISHED |
| Object | gravity-fed water channels |
—
|
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: gravity-fed water channels | Statement: [Tambomachay, hasHydraulicEngineering, gravity-fed water channels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHydraulicEngineering Context triple: [Tambomachay, hasHydraulicEngineering, gravity-fed water channels]
-
A.
hydraulicEngineeringFeature
chosen
Indicates a relationship where something is a structure, system, or element designed or used to control, convey, store, or manage water or other fluids.
-
B.
hasEngineeringBy
Indicates that something is designed, planned, or constructed by a specified engineer or engineering entity.
-
C.
hasEngineeringFunction
Indicates that an entity possesses or performs a specific engineering-related role, purpose, or operational function.
-
D.
hasAqueduct
Indicates that one entity possesses, contains, or is equipped with an aqueduct that serves or passes through it.
-
E.
hasHydroelectricProject
Indicates that an entity is associated with, operates, or contains a hydroelectric power generation project.
- 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_69e0b4b2aa788190ae9eb37c1d73b1f1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69f4066908190a94724697fb8cdcb |
completed | April 20, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:36 a.m.