Triple
T22376203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commended Students |
E553156
|
entity |
| Predicate | documentationProvidedTo |
P75992
|
FINISHED |
| Object | high school officials |
—
|
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: high school officials | Statement: [Commended Students, documentationProvidedTo, high school officials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentationProvidedTo Context triple: [Commended Students, documentationProvidedTo, high school officials]
-
A.
documentationProvidedAt
Indicates that documentation is supplied, made available, or presented at a specific time, place, or context.
-
B.
documentationShownIn
Indicates that certain documentation is displayed or made visible within a particular context, interface, or location.
-
C.
providedInformationTo
chosen
Indicates that one entity has supplied or communicated information to another entity.
-
D.
providedInformationOn
Indicates that one entity supplied or communicated specific information or details to another entity.
-
E.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158285d208190bc7d05d315267995 |
completed | April 29, 2026, 1 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.