Triple
T29341046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Arc Hammer |
E744036
|
entity |
| Predicate | locationDuringGame |
P146339
|
FINISHED |
| Object | near the planet Anteevy |
—
|
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: near the planet Anteevy | Statement: [The Arc Hammer, locationDuringGame, near the planet Anteevy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationDuringGame Context triple: [The Arc Hammer, locationDuringGame, near the planet Anteevy]
-
A.
locationInPlay
chosen
Indicates that an entity is currently situated or active within the defined play area or game environment.
-
B.
gameLocation
Indicates the place or venue where a game or match takes place.
-
C.
game2Location
Indicates that a game takes place at, or is associated with, a specific location.
-
D.
game4Location
Indicates the place or venue where the fourth game in a series or sequence takes place.
-
E.
inGameLocationType
Indicates that an entity has a specific type or category of location within a game world (e.g., city, dungeon, region).
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_6a0017dd31d08190aa5e9f72df83733a |
completed | May 10, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_6a0015a1deb88190b9cdaa60455b0a33 |
completed | May 10, 2026, 5:20 a.m. |
Created at: April 28, 2026, 1:33 p.m.