Triple
T32388205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Tokyo protests of 1968–1969 |
E827593
|
entity |
| Predicate | protestMethods |
P16107
|
FINISHED |
| Object | building occupations |
—
|
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: building occupations | Statement: [University of Tokyo protests of 1968–1969, protestMethods, building occupations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protestMethods Context triple: [University of Tokyo protests of 1968–1969, protestMethods, building occupations]
-
A.
protests
Indicates that an entity publicly expresses opposition or disapproval toward another entity, action, or situation.
-
B.
protestForm
chosen
Indicates the specific method or mode by which a protest or demonstration is carried out.
-
C.
protestFocus
Indicates that a protest is directed toward, concerned with, or centered on a particular issue, target, or subject.
-
D.
protestLedBy
Indicates that a protest is directed or organized under the leadership or guidance of a particular person or group.
-
E.
notableProtest
Indicates that an entity is recognized for having led, organized, or been centrally involved in a significant protest or demonstration.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 12:51 a.m.