Triple
T15200938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agen aqueduct |
E363264
|
entity |
| Predicate | waterwayWidth |
P117097
|
FINISHED |
| Object | 8.8 m |
—
|
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: 8.8 m | Statement: [Agen aqueduct, waterwayWidth, 8.8 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterwayWidth Context triple: [Agen aqueduct, waterwayWidth, 8.8 m]
-
A.
waterwayLengthKilometres
Indicates the total length of a waterway, measured in kilometres.
-
B.
waterwayClass
Indicates the classification or type of a waterway based on its navigational, functional, or physical characteristics.
-
C.
stateWaterway
Indicates that a waterway is located within, passes through, or is otherwise geographically associated with a particular state.
-
D.
waterwaySystem
Indicates that one entity is part of, or belongs to, a connected network of waterways associated with another entity.
-
E.
waterwayAccess
Indicates that one location has direct access to a waterway (such as a river, canal, or sea route) that can be used for transport, navigation, or related activities.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006b588b88190a88e91d521acbdfe |
completed | April 15, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec72059c08190a34f513a00185b08 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:10 a.m.