Triple
T4069314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euromaidan |
E86604
|
entity |
| Predicate | peakNumberOfParticipants |
P23195
|
FINISHED |
| Object | over 800000 in Kyiv |
—
|
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 800000 in Kyiv | Statement: [Euromaidan, peakNumberOfParticipants, over 800000 in Kyiv]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakNumberOfParticipants Context triple: [Euromaidan, peakNumberOfParticipants, over 800000 in Kyiv]
-
A.
numberOfParticipants
Indicates the total count of entities involved in a particular event, activity, or relationship.
-
B.
memberCountAtPeak
Indicates the highest number of members that an entity (such as a group or organization) has had at any point in time.
-
C.
hasParticipants
Indicates that an event, activity, or situation involves one or more entities as participants in it.
-
D.
peakDayAttendance
chosen
Indicates the number of attendees present on the single highest-attendance day within a given period or event.
-
E.
peakUse
Indicates the time, condition, or context in which something reaches its maximum level of use or intensity.
- 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_69aed93ebe448190a1f1686e28740ac9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefbfa45c88190b7b13b35de816378 |
completed | March 9, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69aef9061d2481908307cafc9e9b32c0 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.