Triple
T38669604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mendiola area |
E940543
|
entity |
| Predicate | typicalProtestIssues |
P147134
|
FINISHED |
| Object | tuition fee increases |
—
|
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: tuition fee increases | Statement: [Mendiola area, typicalProtestIssues, tuition fee increases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalProtestIssues Context triple: [Mendiola area, typicalProtestIssues, tuition fee increases]
-
A.
politicalIssueIn
Indicates that a political issue is relevant to, occurs within, or is associated with a particular geographic or political region.
-
B.
protestFocus
chosen
Indicates that a protest is directed toward, concerned with, or centered on a particular issue, target, or subject.
-
C.
protests
Indicates that an entity publicly expresses opposition or disapproval toward another entity, action, or situation.
-
D.
politicalIssueFor
Indicates a relationship where a particular topic, problem, or policy area is considered a matter of political concern or debate for a given entity.
-
E.
socialIssue
Indicates a relationship where something is recognized or treated as a problem or concern affecting society or a community at large.
- 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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:33 p.m.