Triple
T26495909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIDA |
E669280
|
entity |
| Predicate | positionOnIsraeliPalestinianConflict |
P54133
|
FINISHED |
| Object | supports two-state solution |
—
|
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: supports two-state solution | Statement: [FIDA, positionOnIsraeliPalestinianConflict, supports two-state solution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnIsraeliPalestinianConflict Context triple: [FIDA, positionOnIsraeliPalestinianConflict, supports two-state solution]
-
A.
positionOnArabIsraeliConflict
chosen
Indicates a stance or viewpoint that an entity holds regarding the Arab–Israeli conflict.
-
B.
regionOnWestBank
Indicates that one region is located on the western bank of another geographic feature, such as a river or body of water.
-
C.
stateOnWestBank
Indicates that a state is located on the western bank of a specified river or body of water.
-
D.
effectOnPalestinians
Indicates the impact or consequences that an action, event, or condition has on Palestinians.
-
E.
locatedOnSideOfConflict
Indicates that an entity is positioned or aligned on a particular side or faction within a conflict.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 27, 2026, 1:08 a.m.