Triple
T8198037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liberty Plaza Park |
E191482
|
entity |
| Predicate | clearedOfProtestersOn |
P81451
|
FINISHED |
| Object | 2011-11-15 |
—
|
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: 2011-11-15 | Statement: [Liberty Plaza Park, clearedOfProtestersOn, 2011-11-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clearedOfProtestersOn Context triple: [Liberty Plaza Park, clearedOfProtestersOn, 2011-11-15]
-
A.
protests
Indicates that an entity publicly expresses opposition or disapproval toward another entity, action, or situation.
-
B.
teamDuringProtest
Indicates that two or more entities are part of the same team or organized group specifically in the context of a protest event.
-
C.
notableProtest
Indicates that an entity is recognized for having led, organized, or been centrally involved in a significant protest or demonstration.
-
D.
hasProtestMovement
Indicates that an entity is associated with, or gives rise to, an organized protest movement opposing or advocating change related to it.
-
E.
locationOfNotableProtest
Indicates the place where a significant or notable protest event occurred.
- 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_69ca82c6e9548190a4c5ca14516e4417 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5c2341f881908be59c378896e5bc |
completed | March 31, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb46635424819085d086972b264280 |
completed | March 31, 2026, 3:58 a.m. |
Created at: March 30, 2026, 5:42 p.m.