Triple
T19037352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suit of Swords |
E465907
|
entity |
| Predicate | hasElementalAssociation |
P53226
|
FINISHED |
| Object | Air |
—
|
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: Air | Statement: [Suit of Swords, hasElementalAssociation, Air]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElementalAssociation Context triple: [Suit of Swords, hasElementalAssociation, Air]
-
A.
hasRoleInElementals
Indicates that an entity holds a specific role or function within a group, system, or context referred to as "Elementals".
-
B.
elementalPower
Indicates a relationship where an entity possesses, controls, or is associated with a specific elemental force or power.
-
C.
hasMagicSystemElement
Indicates that an entity’s magic system includes or is characterized by a specific elemental component or aspect.
-
D.
hasRitualElements
Indicates that one entity incorporates, contains, or is characterized by ritualistic components, practices, or features associated with formalized ceremonies or rites.
-
E.
elementalAssociation
chosen
Indicates an association where one entity is linked or related to a particular element or elemental property (such as fire, water, earth, or air).
- 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d744b39881909334a80a4c15000b |
completed | April 20, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69e4a3001e388190aa6057266514e75a |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.