Triple
T29548369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Palace |
E749690
|
entity |
| Predicate | previousGovernmentTypeServed |
P117059
|
FINISHED |
| Object | Galactic Republic |
—
|
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: Galactic Republic | Statement: [Imperial Palace, previousGovernmentTypeServed, Galactic Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousGovernmentTypeServed Context triple: [Imperial Palace, previousGovernmentTypeServed, Galactic Republic]
-
A.
servedInGovernmentWith
Indicates that two individuals held positions in the same government or administration during an overlapping period of time.
-
B.
governmentServed
Indicates that a person has held a position serving in or working for a particular government.
-
C.
laterGovernmentType
chosen
Indicates that one government type succeeds or replaces another at a later point in time.
-
D.
governmentTypeServed
Indicates the type of government that an entity serves, is affiliated with, or operates under in its role or function.
-
E.
wasInGovernmentWith
Indicates that two individuals served together within the same government or administration during an overlapping 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: April 28, 2026, 5:10 p.m.