Triple
T38584084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bloodmyst Isle |
E932306
|
entity |
| Predicate | continentMap |
P121983
|
FINISHED |
| Object | Kalimdor world map |
—
|
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: Kalimdor world map | Statement: [Bloodmyst Isle, continentMap, Kalimdor world map]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continentMap Context triple: [Bloodmyst Isle, continentMap, Kalimdor world map]
-
A.
continentMapID
Indicates a mapping relationship that associates an entity with the identifier of the continent it belongs to or is located in.
-
B.
continentDistribution
Indicates how something is geographically distributed or spread across different continents.
-
C.
continentReference
chosen
Indicates that one entity serves as a reference or pointer to a specific continent associated with another entity.
-
D.
continentLocationSymbolized
Indicates that one entity symbolically represents or denotes the continental location of another entity.
-
E.
continentType
Indicates that one entity is classified as a specific type or category of continent in relation to another entity.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: May 3, 2026, 4:32 p.m.