Triple
T20697758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nightcrawler |
E508699
|
entity |
| Predicate | teleportationEffect |
P111256
|
FINISHED |
| Object | sulfurous smell |
—
|
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: sulfurous smell | Statement: [Nightcrawler, teleportationEffect, sulfurous smell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teleportationEffect Context triple: [Nightcrawler, teleportationEffect, sulfurous smell]
-
A.
canTeleport
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.
-
B.
movementEffect
chosen
Indicates how one entity’s movement causes a change or effect in another entity or in the environment.
-
C.
timeTravelDeviceUsed
Indicates that an entity makes use of a device or mechanism that enables travel through time.
-
D.
displacementEffect
Indicates that one entity’s presence, action, or introduction causes another entity to be moved, replaced, or rendered less prominent or effective.
-
E.
timeTravelMethod
Indicates the specific mechanism or technique by which an entity performs or experiences time travel.
- 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_69e0b4c2b2a481909e31e9cb8f81ab55 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c1132178819081086e085f7b3ff8 |
completed | April 21, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:11 p.m.