Triple
T14361980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aqua Anio Vetus |
E356126
|
entity |
| Predicate | carriedWaterMostly |
P113741
|
FINISHED |
| Object | underground |
—
|
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: underground | Statement: [Aqua Anio Vetus, carriedWaterMostly, underground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriedWaterMostly Context triple: [Aqua Anio Vetus, carriedWaterMostly, underground]
-
A.
transportsWaterTo
Indicates that one entity carries or conveys water from its location or source to another entity or destination.
-
B.
usedWaterway
Indicates that one entity traveled, transported goods, or otherwise moved via a particular waterway as the route or medium of use.
-
C.
waterContains
Indicates that a body or volume of water holds, includes, or has within it a specified substance, object, or entity.
-
D.
hasWaterCharacteristics
Indicates that one entity possesses qualities, properties, or behaviors characteristic of water.
-
E.
transportsWaterFrom
Indicates that one entity carries or conveys water from a specified source entity to another location or entity.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8fabec088190bd8128371b29e958 |
completed | April 14, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a9cb3e081909f6b33fdd939bb9e |
completed | April 14, 2026, 11:53 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:15 a.m.