Triple
T18904277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pierce College Fort Steilacoom |
E462413
|
entity |
| Predicate | hasPrimaryStudentType |
P86476
|
FINISHED |
| Object | commuter 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: commuter students | Statement: [Pierce College Fort Steilacoom, hasPrimaryStudentType, commuter students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryStudentType Context triple: [Pierce College Fort Steilacoom, hasPrimaryStudentType, commuter students]
-
A.
hasPrimaryInstitutionType
Indicates that an entity’s main or principal institutional classification or category is of a specified type.
-
B.
hasPrimaryCourse
Indicates that an entity is associated with its main or principal course in a given context (such as a meal, curriculum, or sequence of offerings).
-
C.
hasStudentCategory
Indicates that an entity is classified under a specific category or type of student.
-
D.
primaryStudentType
chosen
Indicates the main or most characteristic type or category of student associated with an entity.
-
E.
hasGradeType
Indicates that an entity is associated with a particular category or type of grade (e.g., letter grade, pass/fail, percentage).
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c52c121c8190a2057b99c723694b |
completed | April 20, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.