Triple
T33118022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Journey into Mystery #103 |
E847509
|
entity |
| Predicate | featuresRaceOrSpecies |
P7733
|
FINISHED |
| Object | Asgardians |
—
|
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: Asgardians | Statement: [Journey into Mystery #103, featuresRaceOrSpecies, Asgardians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresRaceOrSpecies Context triple: [Journey into Mystery #103, featuresRaceOrSpecies, Asgardians]
-
A.
featuresSpecies
chosen
Indicates that something includes, presents, or highlights a particular species as part of its content or composition.
-
B.
hasFictionalSpeciesTrait
Indicates that a fictional species possesses a particular characteristic, feature, or attribute.
-
C.
hasFeatureRace
Indicates that an entity includes, offers, or is associated with a specific race-related feature or race event.
-
D.
raceInLegendarium
Indicates that an entity belongs to a particular fictional race or species within a specific mythological or fantasy legendarium.
-
E.
speciesType
Indicates the specific biological species category to which an entity belongs.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0160834e388190908591b300954d29 |
completed | May 11, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_6a01602a83408190a11d754bdc7da0e9 |
completed | May 11, 2026, 4:50 a.m. |
Created at: May 1, 2026, 1:27 a.m.