Triple
T29655238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warp Gate |
E750245
|
entity |
| Predicate | canWarpIn |
P100766
|
FINISHED |
| Object | Zealot |
—
|
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: Zealot | Statement: [Warp Gate, canWarpIn, Zealot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canWarpIn Context triple: [Warp Gate, canWarpIn, Zealot]
-
A.
hasWarp
Indicates that one entity possesses, is equipped with, or is capable of using a warp or warp-related mechanism in relation to another entity or context.
-
B.
canTeleport
chosen
Indicates that an entity has the ability to instantaneously move itself or something else from one location to another without traversing the space in between.
-
C.
canMove
Indicates that one entity has the ability or permission to change its location or position relative to its environment or another entity.
-
D.
canPass
Indicates that one entity is able or permitted to move through, cross, or successfully traverse another entity or barrier.
-
E.
mayEnterInto
Indicates that one entity is permitted or authorized to form or establish a specified relationship, agreement, or state with 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f66f274ba08190bcdbdfeccf4af09d |
completed | May 2, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:54 p.m.