Triple
T37508869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vigilant Guardian |
E932165
|
entity |
| Predicate | locationWorld |
P50107
|
FINISHED |
| Object | Zereth Mortis |
E931131
|
NE 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: Zereth Mortis | Statement: [Vigilant Guardian, locationWorld, Zereth Mortis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationWorld Context triple: [Vigilant Guardian, locationWorld, Zereth Mortis]
-
A.
positionInWorlds
Indicates that an entity occupies specific spatial coordinates or locations within one or more distinct worlds or environments.
-
B.
countryLocated
Indicates that a country is geographically situated within or associated with a specific larger region, territory, or political entity.
-
C.
locationScrapped
Indicates that the location associated with an entity has been removed, discarded, or is no longer considered valid or in use.
-
D.
worldName
chosen
Indicates that an entity has or is associated with a specific world’s name.
-
E.
locationOnField
Indicates the specific position or area that an entity occupies on a defined field or playing surface.
- F. None of above.
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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40a7e56b34819090426cbc6de5a335 |
completed | June 28, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.