Triple
T22376132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Hispanic Recognition Program |
E553155
|
entity |
| Predicate | recognizedStudentGroup |
P11007
|
FINISHED |
| Object | Hispanic 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: Hispanic students | Statement: [National Hispanic Recognition Program, recognizedStudentGroup, Hispanic students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedStudentGroup Context triple: [National Hispanic Recognition Program, recognizedStudentGroup, Hispanic students]
-
A.
studentGroup
Indicates that an entity is a group or collective of students associated together for a common purpose or activity.
-
B.
targetStudentGroup
chosen
Indicates a relationship where something is directed, tailored, or intended specifically for a particular group of students.
-
C.
associatedStudentBodyName
Indicates the name of the student body that is formally linked or affiliated with a given entity.
-
D.
recognizedAsInstitutionBy
Indicates that an entity is acknowledged or accepted as an institution by a specified recognizing party.
-
E.
representedGroups
Indicates that an entity serves as an official or recognized representative for one or more groups.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158285d208190bc7d05d315267995 |
completed | April 29, 2026, 1 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.