Triple
T4404275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wexner Graduate Fellowship |
E93688
|
entity |
| Predicate | hasBeneficiaryType |
P22506
|
FINISHED |
| Object | graduate students |
—
|
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: graduate students | Statement: [Wexner Graduate Fellowship, hasBeneficiaryType, graduate students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeneficiaryType Context triple: [Wexner Graduate Fellowship, hasBeneficiaryType, graduate students]
-
A.
beneficiaryType
chosen
Indicates the type or category of beneficiary that receives or is intended to receive the benefit or outcome of an action or resource.
-
B.
hasTypeOfRecipient
Indicates that an entity is associated with a specific category or kind of recipient it is intended for or directed to.
-
C.
hasBankType
Indicates that an entity is associated with or classified by a particular type or category of bank.
-
D.
beneficiaryRequirement
Indicates that one entity has a requirement specifying who or what must be the beneficiary of a particular action, service, or resource.
-
E.
beneficiaryRole
Indicates that one entity serves as the beneficiary or recipient of an action, service, or resource provided by another entity.
- 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_69b345158c748190a2c040fce2da9980 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b352d1af608190ac06d50433cf24bb |
completed | March 12, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69b34f5b36a881909bf2e970aa523390 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:28 p.m.