Triple
T30722970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Milagros Aqueduct |
E782201
|
entity |
| Predicate | builtForCity |
P166435
|
FINISHED |
| Object | Emerita Augusta |
—
|
NE NERFINISHED |
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: Emerita Augusta | Statement: [Los Milagros Aqueduct, builtForCity, Emerita Augusta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtForCity Context triple: [Los Milagros Aqueduct, builtForCity, Emerita Augusta]
-
A.
structureBuiltFor
chosen
Indicates that one entity was constructed specifically to serve, house, or support the function, use, or needs of another entity.
-
B.
isBuiltFor
Indicates that one entity is specifically designed, intended, or optimized to serve, support, or accommodate another entity or purpose.
-
C.
roadBuiltFor
Indicates that a road was constructed specifically to serve, provide access to, or support the use or needs of a particular entity.
-
D.
vehicleFor
Indicates that one entity serves as the means of transportation or conveyance for another entity.
-
E.
intendedForVehicle
Indicates that something is designed, meant, or suitable to be used with or by a particular vehicle.
- 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:36 p.m.