Triple
T5811144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taklamakan Desert |
E128869
|
entity |
| Predicate | rankingBySize |
P1174
|
FINISHED |
| Object | one of the largest sandy deserts in the world |
—
|
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: one of the largest sandy deserts in the world | Statement: [Taklamakan Desert, rankingBySize, one of the largest sandy deserts in the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankingBySize Context triple: [Taklamakan Desert, rankingBySize, one of the largest sandy deserts in the world]
-
A.
rankBySize
chosen
Indicates that entities are ordered or compared based on their size.
-
B.
rankByLength
Indicates ordering a set of items based on their length, typically from shortest to longest or vice versa.
-
C.
rankingInCountryBySize
Indicates the position of an entity in an ordered list of entities within a specific country, based on their relative size.
-
D.
regionRankBySize
Indicates the relative ordering of regions based on their physical size, from largest to smallest (or vice versa).
-
E.
rankingType
Indicates the specific basis or method by which items are ordered or ranked relative to one another.
- 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_69c0084788848190bcf71f6bc5d71597 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b538cd08190a7dac378898059b9 |
completed | March 22, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c021d5ecd081908a62dd66e26f8598 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:52 p.m.