Triple
T6302914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garden City Community College |
E141297
|
entity |
| Predicate | accommodatesStudentType |
P5246
|
FINISHED |
| Object | traditional 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: traditional students | Statement: [Garden City Community College, accommodatesStudentType, traditional students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accommodatesStudentType Context triple: [Garden City Community College, accommodatesStudentType, traditional students]
-
A.
studentClassHoused
Indicates that a particular student’s class is accommodated or located within a specific housing or facility.
-
B.
acceptsStudents
Indicates that an institution or program allows and takes in students as participants or members.
-
C.
hasStudentWing
Indicates that an organization or institution includes a dedicated student wing or student-affiliated subdivision.
-
D.
hasStudentBodyType
chosen
Indicates that an educational institution possesses a student body characterized by a particular type or classification.
-
E.
hasStudentCategory
Indicates that an entity is classified under a specific category or type of student.
- 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_69c008cf0ad4819095def81e2bd42f9f |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0645e150881908b49a07914dcbfd8 |
completed | March 22, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69c060e311b48190b1c74a5cf9435623 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:27 p.m.