Triple
T27811231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ajan Kloss |
E702522
|
entity |
| Predicate | galacticConflict |
P164351
|
FINISHED |
| Object | First Order–Resistance war |
E702509
|
NE 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: First Order–Resistance war | Statement: [Ajan Kloss, galacticConflict, First Order–Resistance war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: galacticConflict Context triple: [Ajan Kloss, galacticConflict, First Order–Resistance war]
-
A.
rocketWarOccursBetween
Indicates that a rocket-based military conflict or exchange of rocket fire takes place between the specified entities.
-
B.
inGalacticHemisphere
Indicates that one entity is located within the same specified galactic hemisphere as another entity or reference frame.
-
C.
baseOfOperationsGalaxy
Indicates that a galaxy serves as the primary base of operations or main area of activity for an entity.
-
D.
galacticDestination
Indicates that one entity serves as the target or endpoint location within a galaxy that another entity is directed or traveling toward.
-
E.
inGalacticQuadrant
Indicates that one entity (typically a location or object) is situated within a specified galactic quadrant in space.
- F. None of above. chosen
Provenance (5 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f644de4a84819087ddb84757fc4585 |
completed | May 2, 2026, 6:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a12ecd949688190a88bd50e7a8606df |
completed | May 24, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f643e818d481908fc66bc91bd25d77 |
completed | May 2, 2026, 6:35 p.m. |
Created at: April 27, 2026, 5:42 p.m.