Triple
T18855441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elves |
E461159
|
entity |
| Predicate | typicalAlignmentInFantasy |
P120754
|
FINISHED |
| Object | good |
—
|
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: good | Statement: [Elves, typicalAlignmentInFantasy, good]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAlignmentInFantasy Context triple: [Elves, typicalAlignmentInFantasy, good]
-
A.
typicalAlignment
Indicates the usual or most common way in which two entities are positioned, oriented, or arranged relative to each other.
-
B.
hasAlignmentInFiction
chosen
Indicates that a fictional character, group, or entity possesses a specific moral or ethical alignment within a fictional setting.
-
C.
primaryRaceAlignment
Indicates how an entity’s main racial identity or classification is aligned, categorized, or associated within a defined racial framework or system.
-
D.
eraAlignment
Indicates that two entities are associated with, or correspond to, the same historical or temporal era.
-
E.
speciesAlignment
Indicates how closely related or compatible two species are in terms of traits, behavior, or evolutionary relationship.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c05c16e88190a08b6a8b94e1c9f9 |
completed | April 20, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.