Triple
T15366714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Croton Aqueduct system |
E367432
|
entity |
| Predicate | waterConveyanceMethod |
P14199
|
FINISHED |
| Object | enclosed masonry conduit |
—
|
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: enclosed masonry conduit | Statement: [Croton Aqueduct system, waterConveyanceMethod, enclosed masonry conduit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterConveyanceMethod Context triple: [Croton Aqueduct system, waterConveyanceMethod, enclosed masonry conduit]
-
A.
waterDistributionMethod
Indicates how water is delivered, supplied, or allocated from a source to its intended recipients or locations.
-
B.
transportsWaterTo
chosen
Indicates that one entity carries or conveys water from its location or source to another entity or destination.
-
C.
usedWaterway
Indicates that one entity traveled, transported goods, or otherwise moved via a particular waterway as the route or medium of use.
-
D.
transportsWaterFrom
Indicates that one entity carries or conveys water from a specified source entity to another location or entity.
-
E.
waterRenewalMethod
Indicates the method or process by which water is replenished, refreshed, or renewed in a given context.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e4a7cdc8190b7b48c97e774c306 |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69deca9ab7e88190a9261ef27be665b1 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:18 a.m.