Triple
T6518080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamarod petition campaign |
E148313
|
entity |
| Predicate | signaturesTargetDate |
P71364
|
FINISHED |
| Object | 30 June 2013 |
—
|
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: 30 June 2013 | Statement: [Tamarod petition campaign, signaturesTargetDate, 30 June 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signaturesTargetDate Context triple: [Tamarod petition campaign, signaturesTargetDate, 30 June 2013]
-
A.
dateSigned
Indicates the specific date on which an agreement, document, or contract was formally signed.
-
B.
agreementSignedAt
Indicates the specific time and/or place at which an agreement was formally signed.
-
C.
signedOnSameDayAs
Indicates that two signing events occurred on the same calendar date, regardless of the specific time.
-
D.
holdingDate
Indicates the date on which a holding, possession, or ownership of something is recorded or takes effect.
-
E.
dateSignificance
Indicates the specific importance, meaning, or notable role that a particular date holds within a given context or relationship.
- 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac108abc819082d1368af6611a92 |
completed | March 27, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69c69f362ee4819090e8fa48caef7d7d |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 1:44 p.m.