Triple
T37665854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sand Kingdom |
E937817
|
entity |
| Predicate | containsWorldType |
P203669
|
FINISHED |
| Object | main kingdom |
—
|
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: main kingdom | Statement: [Sand Kingdom, containsWorldType, main kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsWorldType Context triple: [Sand Kingdom, containsWorldType, main kingdom]
-
A.
hasWorld
Indicates that an entity possesses, is associated with, or encompasses a particular world or global context.
-
B.
hasWorldStructure
Indicates that an entity possesses or is characterized by a particular overall world-level organization, framework, or structural configuration.
-
C.
hasWorldMapNodeType
Indicates that something is associated with a specific type or category of node within a world map structure.
-
D.
containsRegionType
Indicates that one region includes or encompasses another region of a specified type within its spatial or logical boundaries.
-
E.
hasFictionalWorldType
Indicates that an entity is associated with, set in, or characterized by a particular type or category of fictional world.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a01c303af6081909c229b2c8e91c680 |
completed | May 11, 2026, 11:52 a.m. |
| PD | Predicate disambiguation | batch_6a01c28ebf54819094318c447d8c7943 |
completed | May 11, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_6a01c302fe4081908ecbff9ae374f80f |
completed | May 11, 2026, 11:52 a.m. |
Created at: May 3, 2026, 4:18 p.m.