Triple
T27872153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crait |
E704817
|
entity |
| Predicate | battleInvolvedFaction |
P99629
|
FINISHED |
| Object | Resistance |
—
|
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: Resistance | Statement: [Crait, battleInvolvedFaction, Resistance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleInvolvedFaction Context triple: [Crait, battleInvolvedFaction, Resistance]
-
A.
battleInvolvedIn
Indicates that an entity participated as a combatant or directly took part in a specific battle or military engagement.
-
B.
battleInvolvedEmpire
Indicates that a particular empire participated as a combatant in the referenced battle.
-
C.
foughtForFaction
Indicates that an entity actively participated in or supported a particular faction, typically in a conflict or struggle.
-
D.
battleRelatedTo
Indicates a relationship where one entity is connected to, associated with, or relevant to a particular battle or combat event.
-
E.
factionInvolved
chosen
Indicates that a particular faction participates in, is associated with, or plays a role in the specified event, situation, or context.
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6397cafe081909ab66f1072c4888d |
completed | May 2, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69f6318be69481909d1bcf29b7b60eb2 |
completed | May 2, 2026, 5:17 p.m. |
Created at: April 27, 2026, 6:25 p.m.