Triple
T5202472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barabbas |
E117424
|
entity |
| Predicate | crowdAction |
P62461
|
FINISHED |
| Object | crowd asked for Barabbas to be released |
—
|
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: crowd asked for Barabbas to be released | Statement: [Barabbas, crowdAction, crowd asked for Barabbas to be released]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crowdAction Context triple: [Barabbas, crowdAction, crowd asked for Barabbas to be released]
-
A.
crowdWas
Indicates that a crowd possessed or exhibited a particular state, quality, or condition.
-
B.
hasCrowdLevel
Indicates the degree or intensity of how crowded a place, event, or situation is.
-
C.
massParticipation
Indicates that a large number of individuals or entities are jointly involved in or contributing to a particular activity, event, or process.
-
D.
teamDuringProtest
Indicates that two or more entities are part of the same team or organized group specifically in the context of a protest event.
-
E.
ledPeopleTo
Indicates that one entity guided, directed, or caused a group of people to move toward or adopt something (such as a place, action, state, or belief).
- F. None of above. chosen
Provenance (4 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_69bd4463dd3c81909966123f20b79d57 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7adb034c819086bf8a85fbf158f4 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77b9a67c8190819612257ea746b4 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd7ad9bdd88190ae8aa6f4aba695a7 |
completed | March 20, 2026, 4:50 p.m. |
Created at: March 20, 2026, 1:47 p.m.