Triple
T37556468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cairo Consensus |
E933710
|
entity |
| Predicate | reframedPolicyFrom |
P188287
|
FINISHED |
| Object | demographic targets |
—
|
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: demographic targets | Statement: [Cairo Consensus, reframedPolicyFrom, demographic targets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reframedPolicyFrom Context triple: [Cairo Consensus, reframedPolicyFrom, demographic targets]
-
A.
reflectsPolicy
Indicates that one entity embodies, represents, or is aligned with the rules, principles, or stance defined by a particular policy.
-
B.
replacedPolicyApproach
Indicates that one policy approach has been superseded and taken the place of another policy approach.
-
C.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
-
D.
referencePolicy
Indicates that one entity defines rules or guidelines governing how another entity may be referred to, cited, or mentioned.
-
E.
inspiredByPolicy
Indicates that an action, decision, or entity is motivated, guided, or shaped by a specific policy or set of policies.
- F. None of above. chosen
Provenance (4 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba61dff5081909fec88a7aeb0c8a1 |
completed | May 6, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69fba350e9a8819095893229d9643572 |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba61d2214819091ae6793bfefb1f0 |
completed | May 6, 2026, 8:35 p.m. |
Created at: May 3, 2026, 4:17 p.m.