Triple
T29754108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mi-go |
E752980
|
entity |
| Predicate | alignmentInMythos |
P74485
|
FINISHED |
| Object | hostile to humanity |
—
|
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: hostile to humanity | Statement: [Mi-go, alignmentInMythos, hostile to humanity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alignmentInMythos Context triple: [Mi-go, alignmentInMythos, hostile to humanity]
-
A.
positionOnMyth
Indicates the relative stance or viewpoint an entity holds regarding a particular myth.
-
B.
alignmentInStory
chosen
Indicates how a character’s moral or ethical stance (e.g., good, neutral, evil) is portrayed within the context of a specific story.
-
C.
alignmentConcept
Indicates a conceptual or abstract relationship of alignment or correspondence between entities, such as agreement, compatibility, or shared orientation in some dimension.
-
D.
eraAlignment
Indicates that two entities are associated with, or correspond to, the same historical or temporal era.
-
E.
alignmentWithLeo
Indicates that an entity’s position, orientation, or behavior is aligned or in agreement with Leo.
- 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f673c9d2a88190965075607fc73061 |
completed | May 2, 2026, 9:59 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:55 p.m.