Triple
T35690733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnin Konn system |
E1031280
|
entity |
| Predicate | governedDuringGalacticCivilWarBy |
P191007
|
FINISHED |
| Object | Galactic Empire |
E209457
|
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: Galactic Empire | Statement: [Burnin Konn system, governedDuringGalacticCivilWarBy, Galactic Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedDuringGalacticCivilWarBy Context triple: [Burnin Konn system, governedDuringGalacticCivilWarBy, Galactic Empire]
-
A.
controllingFactionDuringGalacticCivilWar
chosen
Indicates which faction held control or authority over a given entity during the time period of the Galactic Civil War.
-
B.
roleDuringGalacticCivilWar
Indicates the specific function, position, or involvement an entity had during the Galactic Civil War.
-
C.
associatedRebellion
Indicates a relationship where an entity is linked to, involved in, or connected with a particular rebellion or uprising.
-
D.
inGalacticHemisphere
Indicates that one entity is located within the same specified galactic hemisphere as another entity or reference frame.
-
E.
homeworldDestroyedBy
Indicates that the subject’s homeworld was destroyed by the specified agent or cause.
- F. None of above.
Provenance (4 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a01e4ba62748190a4756689219b6269 |
completed | May 11, 2026, 2:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38729104048190b20cdefbebc27fe0 |
completed | June 21, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_6a01e3fc2d908190a075c7c1549e5640 |
completed | May 11, 2026, 2:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.