Triple
T27706585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pass Laws in South Africa |
E698572
|
entity |
| Predicate | sparkedEvent |
P872
|
FINISHED |
| Object | Sharpeville massacre |
—
|
NE NERFINISHED |
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: Sharpeville massacre | Statement: [Pass Laws in South Africa, sparkedEvent, Sharpeville massacre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sparkedEvent Context triple: [Pass Laws in South Africa, sparkedEvent, Sharpeville massacre]
-
A.
launchEvent
Indicates an event in which something is formally initiated, introduced, or set into operation.
-
B.
triggerEvent
chosen
Indicates that one entity causes or initiates the occurrence of a specific event involving another entity or the system.
-
C.
selectedEvent
Indicates that a particular event has been chosen or designated from a set of possible events.
-
D.
inspiredEvent
Indicates that one event served as the motivation, cause, or creative stimulus for another event to occur or be conceived.
-
E.
triggered
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f635c7005c8190860c9b01366c286a |
completed | May 2, 2026, 5:35 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 3 p.m.