Triple
T11528772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Aral Sea |
E273363
|
entity |
| Predicate | wasLargerIn |
P42635
|
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: [South Aral Sea, wasLargerIn, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasLargerIn Context triple: [South Aral Sea, wasLargerIn, 20th century]
-
A.
wasLargestOfItsType
chosen
Indicates that an entity held the greatest size, extent, or magnitude among all entities of the same type or category during a given time period.
-
B.
wasIn
Indicates that an entity existed, occurred, or was located within a particular place or context during a specified time or situation.
-
C.
wouldHaveBeenLargest
Indicates that something would have been the largest among a set of entities or options under certain hypothetical or unrealized conditions.
-
D.
wasPrecededBy
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
E.
wasPowerfulIn
Indicates that an entity possessed significant power, influence, or effectiveness within a specified domain, context, or time period.
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d883972b10819093bd09cf8406671c |
completed | April 10, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69d80879fdb48190be6dacc8aa63c809 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.