Triple
T26877294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Zaysan |
E676786
|
entity |
| Predicate | ancient |
P64431
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lake Zaysan, ancient, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ancient Context triple: [Lake Zaysan, ancient, true]
-
A.
isAncient
chosen
Indicates that the entity existed or originated in a very distant past, typically far earlier than the commonly referenced historical period.
-
B.
fellInAntiquity
Indicates that an entity experienced a fall, collapse, or defeat during ancient times.
-
C.
ancientCity
Indicates that the subject is a historically old or long-established city, typically originating from ancient times.
-
D.
ancientLanguages
Indicates that the related entities are languages that originated in and were used during ancient historical periods.
-
E.
ancientStates
Indicates that the related entity functioned as a state or political entity in ancient times.
- 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61f19a7588190b11555c673bbf6a3 |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:36 a.m.