Triple
T31917124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keystone Exams |
E814861
|
entity |
| Predicate | hasAccommodations |
P181081
|
FINISHED |
| Object | students with disabilities |
—
|
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: students with disabilities | Statement: [Keystone Exams, hasAccommodations, students with disabilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccommodations Context triple: [Keystone Exams, hasAccommodations, students with disabilities]
-
A.
hasAccommodation
Indicates that an entity provides, owns, or is associated with a place for someone to stay or live.
-
B.
hasAccommodationAtEndpoints
Indicates that the endpoints of something (e.g., a route, connection, or segment) each have available accommodation facilities.
-
C.
hasTouristAccommodationType
Indicates that an entity provides or is classified by a specific type or category of tourist accommodation.
-
D.
sleepingAccommodation
Indicates that one entity serves as a place or facility where another entity can sleep or stay overnight.
-
E.
hasLodgeType
Indicates that an entity is associated with or classified by a particular type or category of lodge.
- F. None of above. chosen
Provenance (4 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
| PDg | Predicate description generation | batch_69f760a2a90c8190b8fbc55412ab752b |
completed | May 3, 2026, 2:50 p.m. |
Created at: May 1, 2026, 12:02 a.m.