Triple
T29188892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lothal |
E739940
|
entity |
| Predicate | laterControllingFaction |
P169301
|
FINISHED |
| Object | Rebel Alliance |
—
|
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: Rebel Alliance | Statement: [Lothal, laterControllingFaction, Rebel Alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterControllingFaction Context triple: [Lothal, laterControllingFaction, Rebel Alliance]
-
A.
controlledByFaction
Indicates that an entity is under the authority, influence, or governance of a particular faction.
-
B.
hasOpposingFaction
Indicates that one faction stands in opposition or conflict to another faction.
-
C.
expansionFaction
Indicates a relationship where one faction is the expanding or outward-growing counterpart of another faction.
-
D.
controllingFactionDuringGalacticCivilWar
Indicates which faction held control or authority over a given entity during the time period of the Galactic Civil War.
-
E.
territoryLaterControlledBy
chosen
Indicates that a territory was subsequently governed, ruled, or administered by a specified controlling entity after an earlier period.
- 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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
Created at: April 28, 2026, 12:01 p.m.