Triple
T35490223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unification War |
E1025712
|
entity |
| Predicate | goalOfIndependents |
P4658
|
FINISHED |
| Object | maintain autonomy of outer planets |
—
|
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: maintain autonomy of outer planets | Statement: [Unification War, goalOfIndependents, maintain autonomy of outer planets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalOfIndependents Context triple: [Unification War, goalOfIndependents, maintain autonomy of outer planets]
-
A.
postIndependenceGoal
Indicates the aims or objectives pursued after achieving independence.
-
B.
ideologicalGoal
Indicates that an entity aims to promote, realize, or advance a particular ideology or set of ideological principles.
-
C.
independencePolicy
Indicates that an entity has a policy or formal stance aimed at maintaining its autonomy and freedom from control or influence by another entity.
-
D.
politicalGoal
chosen
Indicates a relationship where an entity aims to achieve, promote, or realize a specific political outcome, policy, or state of affairs.
-
E.
representsIndependence
Indicates that one entity embodies, symbolizes, or confers independence in relation to another entity.
- 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_69f76dfbcdd881908c7b0b6bc502252b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.