Triple
T2183403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Texcoco |
E49096
|
entity |
| Predicate | mostlyDrainedBy |
P30644
|
FINISHED |
| Object | 20th 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: 20th century | Statement: [Lake Texcoco, mostlyDrainedBy, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mostlyDrainedBy Context triple: [Lake Texcoco, mostlyDrainedBy, 20th century]
-
A.
drainedSince
chosen
Indicates that one entity has had its contents or resources removed starting from a specific point in time.
-
B.
isTypicallyFilledWith
Indicates that one entity is commonly or usually occupied, loaded, or contained by another entity.
-
C.
pouredOutBy
Indicates that a substance or liquid was released or emptied from a container or source by a particular agent or entity.
-
D.
drunkWith
Indicates that one entity is intoxicated as a result of consuming a particular alcoholic beverage or substance associated with another entity.
-
E.
historicallyEmptiedInto
Indicates that a body of water or watercourse previously discharged its flow into another body of water or location in the past, though this outflow may have since changed.
- 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_69a88aa72d348190a9544bb5b8a4e71d |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc4358fc88190a6f556c2de9fef8c |
completed | March 7, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69abbda0ec948190be88c1243d81a423 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.