Triple
T3646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COFHE |
E68
|
entity |
| Predicate | dataUse |
P399
|
FINISHED |
| Object | benchmarking among member institutions |
—
|
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: benchmarking among member institutions | Statement: [COFHE, dataUse, benchmarking among member institutions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataUse Context triple: [COFHE, dataUse, benchmarking among member institutions]
-
A.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
B.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
C.
usesComputationMethod
Indicates that an entity performs its processing or decision-making by applying a specified computational method or algorithm.
-
D.
grantedTo
Indicates that a right, permission, or resource has been formally given or assigned by one party to another.
-
E.
computes
Indicates that one entity performs a calculation or processing operation to produce a result from given data or inputs.
- 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_69a238d6b47881909e68288aed2fd858 |
completed | Feb. 28, 2026, 12:37 a.m. |
| NER | Named-entity recognition | batch_69a23bcc8eb48190b897cc331563980a |
completed | Feb. 28, 2026, 12:50 a.m. |
| PD | Predicate disambiguation | batch_69a23994309081909ff3e869deef2156 |
completed | Feb. 28, 2026, 12:40 a.m. |
| PDg | Predicate description generation | batch_69a23bcb4bbc819093775f623998d62d |
completed | Feb. 28, 2026, 12:50 a.m. |
Created at: Feb. 28, 2026, 12:40 a.m.