Triple
T37872501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shado-Pan Monastery |
E944639
|
entity |
| Predicate | expansionSettingContinent |
P193449
|
FINISHED |
| Object | Pandaria |
—
|
NE NERFINISHED |
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: Pandaria | Statement: [Shado-Pan Monastery, expansionSettingContinent, Pandaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionSettingContinent Context triple: [Shado-Pan Monastery, expansionSettingContinent, Pandaria]
-
A.
expansionRegion
Indicates a region or area into which something (such as a structure, process, or influence) is intended or allowed to expand.
-
B.
alsoContinent
Indicates that two entities share the same continent or that one entity is located on a continent in addition to another.
-
C.
continentScope
Indicates that something applies within, is limited to, or is defined at the level of a specific continent.
-
D.
expandedTerritoryOf
Indicates that one entity has increased or extended the geographic or jurisdictional area belonging to another entity.
-
E.
continentConfiguration
Indicates how landmasses and oceans are spatially arranged and distributed on a planet’s surface at a given time.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
| PDg | Predicate description generation | batch_69fd474a71648190b6b6ae4991db81b1 |
completed | May 8, 2026, 2:15 a.m. |
Created at: May 3, 2026, 4:19 p.m.