Triple
T35471002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Independents |
E1025206
|
entity |
| Predicate | enemyGovernment |
P143447
|
FINISHED |
| Object | Union of Allied Planets |
—
|
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: Union of Allied Planets | Statement: [Independents, enemyGovernment, Union of Allied Planets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enemyGovernment Context triple: [Independents, enemyGovernment, Union of Allied Planets]
-
A.
combatantGovernment
chosen
Indicates that a government is a direct participant or party in a conflict, war, or combat situation.
-
B.
enemyNation
Indicates that one nation is considered a hostile or adversarial state in relation to another nation.
-
C.
enemyOrganization
Indicates that one organization is considered an adversary or opponent of another organization, typically in a hostile or competitive context.
-
D.
archenemyOf
Indicates a relationship in which one entity is the principal or most important enemy of another, often characterized by deep, ongoing opposition or rivalry.
-
E.
opponentGovernmentType
Indicates the form or system of government of an opposing or rival entity in a given 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.