Triple
T28871007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirkpatrick Choir |
E732142
|
entity |
| Predicate | associatedStudentGroup |
P125547
|
FINISHED |
| Object | Rutgers University Glee Club |
E198780
|
NE 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: Rutgers University Glee Club | Statement: [Kirkpatrick Choir, associatedStudentGroup, Rutgers University Glee Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedStudentGroup Context triple: [Kirkpatrick Choir, associatedStudentGroup, Rutgers University Glee Club]
-
A.
associatedStudentBodyName
Indicates the name of the student body that is formally linked or affiliated with a given entity.
-
B.
associatedWithSchool
Indicates a relationship where an entity has a connection or affiliation with a particular school, such as attendance, employment, or partnership.
-
C.
studentGroup
chosen
Indicates that an entity is a group or collective of students associated together for a common purpose or activity.
-
D.
associatedWithTypeOfSchool
Indicates that an entity has an association or connection with a particular type or category of school.
-
E.
hasStudentGrouping
Indicates that an entity is associated with a particular way of organizing or grouping students.
- F. None of above.
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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a02145017b08190bd424cc647c08d3b |
completed | May 11, 2026, 5:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a24d3fabe5c819088a22bd89d3a0c0c |
completed | June 7, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_6a021338e2b08190980c489ee44c18b3 |
completed | May 11, 2026, 5:34 p.m. |
Created at: April 28, 2026, 7:32 a.m.