Triple
T1795106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trinity School (New York City) |
E39584
|
entity |
| Predicate | collegePreparatoryFocus |
P6235
|
FINISHED |
| Object | humanities |
—
|
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: humanities | Statement: [Trinity School (New York City), collegePreparatoryFocus, humanities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collegePreparatoryFocus Context triple: [Trinity School (New York City), collegePreparatoryFocus, humanities]
-
A.
collegeCoach
Indicates that one entity serves as a coach for a college-level sports team associated with another entity.
-
B.
educationalFocus
chosen
Indicates the primary subject area or theme that an educational activity, program, or resource is centered on.
-
C.
college
Indicates that an entity is a college-level educational institution attended by or associated with another entity.
-
D.
collegeAchievement
Indicates that an entity has attained a specific level of success, recognition, or accomplishment in a college or higher-education context.
-
E.
connectsToCollege
Indicates a relationship where an entity has a direct link, affiliation, or pathway to a college.
- 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_69a88631854081909723959921e45c2b |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab61b6ea188190aab9fb839bf1e367 |
completed | March 6, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69aa61d2f7a8819090301f92d3e358c7 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:32 p.m.