Triple
T38481803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperium |
E915696
|
entity |
| Predicate | notableTargetWorld |
P204680
|
FINISHED |
| Object | Veldt |
E2267515
|
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: Veldt | Statement: [Imperium, notableTargetWorld, Veldt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTargetWorld Context triple: [Imperium, notableTargetWorld, Veldt]
-
A.
notableTarget
Indicates that the subject is particularly significant, prominent, or noteworthy with respect to the specified target.
-
B.
notableWorld
Indicates that an entity is notably recognized or significant on a global or worldwide scale.
-
C.
notableTargetType
Indicates that the subject is notable or significant specifically in relation to entities of the given target type.
-
D.
notableTargetArea
Indicates that an action, effect, or focus is specifically directed toward a particularly important or prominent area or region.
-
E.
notableGameWorld
Indicates that a game’s world or setting is particularly significant, distinguished, or noteworthy in some meaningful way.
- F. None of above. chosen
Provenance (5 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41ccc2f7b08190bb8562eb008f63fa |
completed | June 29, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:31 p.m.