Triple
T25109010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1965 Pakistani presidential election |
E628941
|
entity |
| Predicate | oppositionSupportBase |
P157942
|
FINISHED |
| Object | students |
—
|
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: students | Statement: [1965 Pakistani presidential election, oppositionSupportBase, students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oppositionSupportBase Context triple: [1965 Pakistani presidential election, oppositionSupportBase, students]
-
A.
oppositionSupportBase
chosen
Indicates that an entity serves as a primary source of backing or strength for an opposing side or rival group.
-
B.
supportAgainst
Indicates providing help, resources, or advocacy to oppose or resist a particular target, threat, or adversary.
-
C.
oppositionTheme
Indicates that one entity thematically represents or embodies opposition or conflict in relation to another entity.
-
D.
opposition
Indicates a relationship in which one entity actively resists, disagrees with, or is positioned against another entity, idea, or action.
-
E.
oppositionAlliance
Indicates a relationship where entities form or belong to an alliance that is collectively opposed to another entity or group.
- 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f46575833481908a6ddd1e9a3c5c41 |
completed | May 1, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:26 a.m.