Triple
T2370024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People Power Revolution |
E46064
|
entity |
| Predicate | participantEstimate |
P3846
|
FINISHED |
| Object | over one million people |
—
|
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: over one million people | Statement: [People Power Revolution, participantEstimate, over one million people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participantEstimate Context triple: [People Power Revolution, participantEstimate, over one million people]
-
A.
estimatedCost
Indicates the predicted or calculated monetary amount expected to be required for something, such as a project, item, or action.
-
B.
approximates
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
-
C.
estimatedCostComment
Indicates a textual note or explanation associated with an estimated cost, such as rationale, assumptions, or additional details about that estimate.
-
D.
approximateAudienceSize
chosen
Indicates an estimated number of individuals or entities that are expected to be reached or affected in a given context.
-
E.
surveyParticipants
Indicates that certain entities take part in or respond to a survey.
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc76f5aec8190867d621e6849258c |
completed | March 7, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69abc59b88348190a2d6c08f69974117 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:56 p.m.