Triple
T1459868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cal–Stanford Big Game |
E31485
|
entity |
| Predicate | studentInvolvement |
P4470
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Cal–Stanford Big Game, studentInvolvement, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studentInvolvement Context triple: [Cal–Stanford Big Game, studentInvolvement, high]
-
A.
hasStudentOrganization
Indicates that an entity (such as an institution or department) is associated with or hosts a particular student organization.
-
B.
studentBodyFocus
Indicates that the primary attention, concern, or efforts are directed toward the student body as a whole.
-
C.
involvesInstitution
Indicates that an action, event, or relationship includes or is associated with an institution as a participating party.
-
D.
participation
chosen
Indicates that an entity takes part in, contributes to, or is involved in a shared activity, event, or process with others.
-
E.
facultyStudentInteraction
Indicates interactions, communications, or engagements that occur between faculty members and students.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c59d6dd88190b8ff3bda90aef7e2 |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47ec5108190b1772237f2e5d90b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.