Triple
T31676352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 27th Parliament of Turkey |
E808408
|
entity |
| Predicate | hasOppositionAlliance |
P78166
|
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: [27th Parliament of Turkey, hasOppositionAlliance, Nation Alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOppositionAlliance Context triple: [27th Parliament of Turkey, hasOppositionAlliance, Nation Alliance]
-
A.
hasOpposingAlliance
Indicates that two entities belong to alliances or factions that are in direct opposition or conflict with each other.
-
B.
hasOpposingSide
Indicates that one entity possesses or is associated with another entity that lies on the opposite or facing side relative to a reference orientation or boundary.
-
C.
hasOppositionType
Indicates that an entity is associated with a specific kind or category of opposition it faces or represents.
-
D.
hasOppositionCoalition
chosen
Indicates that a political entity faces an organized coalition of opposing parties or groups.
-
E.
hasOpposingAgent
Indicates that an entity is opposed or counteracted by another agent in a given context or interaction.
- 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 30, 2026, 11:03 p.m.