Triple
T6367143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mongol Empire |
E143254
|
entity |
| Predicate | peakArea |
P70232
|
FINISHED |
| Object | over 24 million square kilometers |
—
|
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: over 24 million square kilometers | Statement: [Mongol Empire, peakArea, over 24 million square kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakArea Context triple: [Mongol Empire, peakArea, over 24 million square kilometers]
-
A.
peakUse
Indicates the time, condition, or context in which something reaches its maximum level of use or intensity.
-
B.
peakApproximateMa
Indicates that one entity’s peak value is approximately equal to another entity’s peak value.
-
C.
peakType
Indicates the specific classification or category of a peak based on its form, prominence, or other defining characteristics.
-
D.
parentPeak
Indicates that one peak is the higher or primary peak to which another, subordinate peak is topographically related.
-
E.
coreAreaOf
Indicates that one entity is the central, primary, or most important area or domain of focus for another entity.
- 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_69c008d8c61081908bcaf61510d881ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06811de2881909ead116117956981 |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623bb29081908bfdfb84a07ece90 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:32 p.m.