Triple
T35490245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unification War |
E1025712
|
entity |
| Predicate | foughtByOrganization |
P183348
|
FINISHED |
| Object | Anglo-Sino 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: Anglo-Sino Alliance | Statement: [Unification War, foughtByOrganization, Anglo-Sino Alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foughtByOrganization Context triple: [Unification War, foughtByOrganization, Anglo-Sino Alliance]
-
A.
foughtInOrganization
Indicates that an individual actively participated in combat or military operations as a member of the specified organization.
-
B.
foughtForFaction
Indicates that an entity actively participated in or supported a particular faction, typically in a conflict or struggle.
-
C.
foughtAs
Indicates that an entity participated in a conflict or war in the capacity, role, or identity specified by another entity.
-
D.
resistanceOrganization
Indicates an organization that actively opposes, resists, or fights against a dominant power, regime, or occupying force.
-
E.
enemyOrganization
Indicates that one organization is considered an adversary or opponent of another organization, typically in a hostile or competitive context.
- F. None of above. chosen
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_69f76dfbcdd881908c7b0b6bc502252b |
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. |
| PDg | Predicate description generation | batch_69f79da8d8848190ab5ab1bdad95d58c |
completed | May 3, 2026, 7:10 p.m. |
Created at: May 3, 2026, 4:04 p.m.