Triple
T17628008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dwight Hall at Yale |
E429899
|
entity |
| Predicate | coordinatesStudentGroups |
P17051
|
FINISHED |
| Object | service organizations |
—
|
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: service organizations | Statement: [Dwight Hall at Yale, coordinatesStudentGroups, service organizations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinatesStudentGroups Context triple: [Dwight Hall at Yale, coordinatesStudentGroups, service organizations]
-
A.
studentGroup
Indicates that an entity is a group or collective of students associated together for a common purpose or activity.
-
B.
associatedStudentBodyName
Indicates the name of the student body that is formally linked or affiliated with a given entity.
-
C.
campusOrganization
chosen
Indicates that one entity is an organization that operates within, is based at, or is formally affiliated with a particular campus.
-
D.
studentSection
Indicates a relationship where a student is enrolled in or associated with a particular course section.
-
E.
boardingGroups
Indicates that certain entities are assigned to or associated with specific boarding groups for an ordered boarding process.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46dbe3a308190a818d04f1a9b15f7 |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:52 a.m.