Triple
T7514345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valens Aqueduct |
E177601
|
entity |
| Predicate | endConstruction |
P1511
|
FINISHED |
| Object | late 4th century |
—
|
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: late 4th century | Statement: [Valens Aqueduct, endConstruction, late 4th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endConstruction Context triple: [Valens Aqueduct, endConstruction, late 4th century]
-
A.
constructionCompleted
chosen
Indicates that a construction process or project has been fully finished and reached its completed state.
-
B.
demolitionEnd
Indicates the point in time or event at which a demolition process is completed or comes to an end.
-
C.
hasConstruction
Indicates that one entity possesses, contains, or is characterized by a particular construction, structure, or built form associated with it.
-
D.
startConstruction
Indicates that an entity initiates the process of building or constructing another entity or structure.
-
E.
constructionCompletedUnder
Indicates that the completion of a construction project occurred under the responsibility, authority, or supervision of a specified agent, organization, or governing body.
- 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_69c69f2891148190a484f3b8222c6f1b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f5d6ccb08190a568a9b58bfbd0cc |
completed | March 27, 2026, 9:25 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d44e9481909813e073b194f6f4 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:45 p.m.