Triple
T28511509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monday Demonstrations (1989) |
E721500
|
entity |
| Predicate | laterNumberOfParticipants |
P142973
|
FINISHED |
| Object | hundreds of thousands |
—
|
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: hundreds of thousands | Statement: [Monday Demonstrations (1989), laterNumberOfParticipants, hundreds of thousands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterNumberOfParticipants Context triple: [Monday Demonstrations (1989), laterNumberOfParticipants, hundreds of thousands]
-
A.
numberOfParticipants
Indicates the total count of entities involved in a particular event, activity, or relationship.
-
B.
hasParticipants
Indicates that an event, activity, or situation involves one or more entities as participants in it.
-
C.
vowOfParticipants
Indicates that certain participants formally promise or commit themselves to a specified action, condition, or relationship.
-
D.
estimatedParticipation
chosen
Indicates an approximate or predicted level, amount, or likelihood of an entity’s involvement in a given activity or event.
-
E.
laterNumber
Indicates that one number occurs or is positioned later than another in a specified ordering or sequence.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: April 28, 2026, 3:12 a.m.