Triple
T38372102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | murder of George Floyd |
E892611
|
entity |
| Predicate | triggeredMovement |
P12894
|
FINISHED |
| Object | Black Lives Matter protests |
—
|
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: Black Lives Matter protests | Statement: [murder of George Floyd, triggeredMovement, Black Lives Matter protests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triggeredMovement Context triple: [murder of George Floyd, triggeredMovement, Black Lives Matter protests]
-
A.
trapMovement
Indicates that an entity restricts, hinders, or immobilizes the movement of another entity, as if trapping it.
-
B.
movementCause
chosen
Indicates that one entity’s action or event is the cause of another entity’s movement or change in location.
-
C.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
-
D.
isMovement
Indicates that the subject undergoes or performs a change in position or location over time.
-
E.
movementType
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
- 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.