Triple
T5338589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Copais |
E123885
|
entity |
| Predicate | eraOfMajorDrainageWorks |
P63075
|
FINISHED |
| Object | late 19th 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 19th century | Statement: [Lake Copais, eraOfMajorDrainageWorks, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfMajorDrainageWorks Context triple: [Lake Copais, eraOfMajorDrainageWorks, late 19th century]
-
A.
isMajorWatercourseOf
Indicates that a watercourse is a primary or significant river or stream associated with, or flowing through, a particular geographic area or feature.
-
B.
watercourseHasDam
Indicates that a watercourse (such as a river or stream) has a dam constructed on or across it.
-
C.
isTributaryDamOf
Indicates that a dam is constructed on and regulates the flow of a tributary river or stream relative to a main watercourse.
-
D.
inflowWatercourse
Indicates that one watercourse flows into or feeds another water body or watercourse.
-
E.
drainageDivideOf
Indicates that one geographic feature functions as the drainage divide (separating water flow into different basins) for another feature or area.
- 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_69bd464b07f8819095aa76577c9829e4 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85e86edc81908d87933db6489f91 |
completed | March 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69bd845a62b081909782863865b257a9 |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd85e69e808190b29548670fd2900a |
completed | March 20, 2026, 5:37 p.m. |
Created at: March 20, 2026, 2 p.m.