Triple
T18770031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayman Nour |
E458992
|
entity |
| Predicate | hasPoliticalStanceOn |
P56202
|
FINISHED |
| Object | democratization of Egypt |
—
|
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: democratization of Egypt | Statement: [Ayman Nour, hasPoliticalStanceOn, democratization of Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoliticalStanceOn Context triple: [Ayman Nour, hasPoliticalStanceOn, democratization of Egypt]
-
A.
policyStance
Indicates the position or viewpoint an entity holds regarding a specific policy or set of policies.
-
B.
reflectsPoliticalViewsOf
Indicates that one entity’s opinions, statements, or representations express or mirror the political views held by another entity.
-
C.
editorialStance
Indicates the position, viewpoint, or bias an editor or publication adopts toward a subject, issue, or entity.
-
D.
mediaStance
Indicates the position, attitude, or bias that a media source expresses toward a subject, event, or entity.
-
E.
hasPoliticalPositionOn
chosen
Indicates that an entity holds or expresses a specific stance, view, or opinion regarding a political issue, policy, or topic.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e58d8782b4819080513fb46798c4db |
completed | April 20, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.