Triple
T4544769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egyptian constitutional referendum, 2011 |
E110018
|
entity |
| Predicate | approvalRate |
P57627
|
FINISHED |
| Object | approximately 77 percent |
—
|
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: approximately 77 percent | Statement: [Egyptian constitutional referendum, 2011, approvalRate, approximately 77 percent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approvalRate Context triple: [Egyptian constitutional referendum, 2011, approvalRate, approximately 77 percent]
-
A.
approvalStatus
Indicates the current state of authorization or acceptance granted to an entity or action.
-
B.
approvedAt
Indicates the date and time at which an entity received formal approval.
-
C.
approvedBy
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
D.
approvalRequirement
Indicates that one entity must grant permission or authorization before another entity’s action, decision, or state change can proceed.
-
E.
approvalMethod
Indicates the method or process by which approval is granted or obtained between entities.
- 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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57d62a8481909d5d803a582c76a1 |
completed | March 20, 2026, 2:21 p.m. |
| PD | Predicate disambiguation | batch_69bd5220e40481908ca2d7e2c43d8531 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56f6e75481909c487a94a2c2d0ba |
completed | March 20, 2026, 2:17 p.m. |
Created at: March 20, 2026, 1:05 p.m.