Triple
T26524780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People’s Alliance |
E670657
|
entity |
| Predicate | opposesAlliance |
P42770
|
FINISHED |
| Object | Nation 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: Nation Alliance | Statement: [People’s Alliance, opposesAlliance, Nation Alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposesAlliance Context triple: [People’s Alliance, opposesAlliance, Nation Alliance]
-
A.
opposingAlliance
chosen
Indicates that two entities belong to rival or mutually opposed alliances or factions.
-
B.
oppositionAlliance
Indicates a relationship where entities form or belong to an alliance that is collectively opposed to another entity or group.
-
C.
alliance
Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
-
D.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
E.
allianceSupport
Indicates a cooperative relationship where one party provides assistance, resources, or backing to an ally within the context of an alliance.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 1:31 a.m.