Triple
T7702649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | March 8 Alliance |
E174536
|
entity |
| Predicate | foreignAlignment |
P52993
|
FINISHED |
| Object | pro-Syria |
—
|
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: pro-Syria | Statement: [March 8 Alliance, foreignAlignment, pro-Syria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foreignAlignment Context triple: [March 8 Alliance, foreignAlignment, pro-Syria]
-
A.
countryAlignment
chosen
Indicates the geopolitical or ideological stance of a country in relation to other countries, blocs, or global power structures.
-
B.
alignedAgainst
Indicates that two or more entities are united in opposition to a common target, side, or objective.
-
C.
foreignInfluence
Indicates that one entity exerts influence, control, or significant impact on another entity from a different country or external origin.
-
D.
foreignPolicyArea
Indicates the specific domain or topic within foreign policy to which an action, decision, or statement is related.
-
E.
typicalAlignment
Indicates the usual or most common way in which two entities are positioned, oriented, or arranged relative to each other.
- 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_69c6995a72cc8190998e56daa6f8e453 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c70165e78c8190bf6b3c34e243cb81 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:03 p.m.