Triple
T23932420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaya |
E602535
|
entity |
| Predicate | alignmentContext |
P16437
|
FINISHED |
| Object | War of the Spark |
—
|
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: War of the Spark | Statement: [Kaya, alignmentContext, War of the Spark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alignmentContext Context triple: [Kaya, alignmentContext, War of the Spark]
-
A.
alignmentRelation
Indicates that one entity is positioned, oriented, or arranged in a specific way relative to another entity.
-
B.
alignmentRange
Indicates a relationship where one entity’s alignment or position is constrained to fall within a specified range defined by another entity or set of parameters.
-
C.
alignmentConcept
chosen
Indicates a conceptual or abstract relationship of alignment or correspondence between entities, such as agreement, compatibility, or shared orientation in some dimension.
-
D.
alignmentGoal
Indicates that an entity has a desired or target alignment state it aims to achieve or maintain.
-
E.
alignedAgainst
Indicates that two or more entities are united in opposition to a common target, side, or objective.
- 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_69e2953cf6e081909b8e25a10a52dddc |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1cf9ce6b8819093fc5e44b1ed137f |
completed | April 29, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:58 p.m.