Triple
T31727417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolokotrones-endowed academic positions |
E809764
|
entity |
| Predicate | fundingUsedFor |
P171559
|
FINISHED |
| Object | faculty salary support |
—
|
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: faculty salary support | Statement: [Kolokotrones-endowed academic positions, fundingUsedFor, faculty salary support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fundingUsedFor Context triple: [Kolokotrones-endowed academic positions, fundingUsedFor, faculty salary support]
-
A.
usedFundingFrom
Indicates that one entity utilized financial resources that originated from another entity.
-
B.
usedFund
Indicates that one entity expended or applied a particular fund or financial resource for some purpose.
-
C.
mainUseOfFunds
chosen
Indicates how the primary portion of allocated or received funds is intended to be used or applied.
-
D.
additionalFundingPurpose
Indicates the specific reason or intended use for which additional funding is sought or allocated beyond the original amount.
-
E.
incomeUsedFor
Indicates that some or all of an income amount is allocated or spent for a specified purpose, activity, or recipient.
- 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_69f348e009c8819095d77df52c645b9c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:20 p.m.