Triple
T5856702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trevor Zoo at Hotchkiss |
E130170
|
entity |
| Predicate | isAccredited |
P67515
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Trevor Zoo at Hotchkiss, isAccredited, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAccredited Context triple: [Trevor Zoo at Hotchkiss, isAccredited, true]
-
A.
hasAccreditationType
Indicates that an entity holds or is associated with a specific category or kind of accreditation.
-
B.
accreditedTo
Indicates that official recognition, authorization, or credit for something is granted by or associated with a particular entity.
-
C.
mayAlsoBeAccreditedTo
Indicates that the credit or attribution for something can additionally be assigned to another entity beyond the primary one.
-
D.
usesAccreditationStandard
Indicates that one entity applies, follows, or bases its processes or evaluations on a specified accreditation standard.
-
E.
hasAccreditationProcess
Indicates that an entity follows or is subject to a formal procedure for obtaining official recognition or accreditation.
- 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_69c0084de39081909eb34e6bed74215a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03345ca0c819081c81148d054fed2 |
completed | March 22, 2026, 6:21 p.m. |
| PDg | Predicate description generation | batch_69c044a9c4f0819081b8c196932883f6 |
completed | March 22, 2026, 7:36 p.m. |
Created at: March 22, 2026, 3:55 p.m.