Triple
T33211514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tulsa Library Trust |
E850173
|
entity |
| Predicate | hasEndowments |
P192163
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tulsa Library Trust, hasEndowments, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndowments Context triple: [Tulsa Library Trust, hasEndowments, yes]
-
A.
hasEndowmentType
Indicates that an entity is associated with a particular category or type of endowment.
-
B.
isEndowedBy
Indicates that something receives its funding, resources, or support from a particular source.
-
C.
hasEndowmentBeneficiary
Indicates that an entity is designated to receive benefits or distributions from another entity’s endowment.
-
D.
hasAllotments
Indicates that one entity has been assigned or granted specific portions, shares, or allocations of something (such as resources, land, or tasks).
-
E.
hasOriginalEndowmentPurpose
Indicates that an entity’s original endowment is intended or designated to serve a specific purpose or function.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
| PDg | Predicate description generation | batch_69fcf82405c88190a19cecf8e9cc272d |
completed | May 7, 2026, 8:37 p.m. |
Created at: May 1, 2026, 1:30 a.m.