Triple
T22897431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moody Foundation |
E568211
|
entity |
| Predicate | notableGrantArea |
P150163
|
FINISHED |
| Object | higher education in Texas |
—
|
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: higher education in Texas | Statement: [Moody Foundation, notableGrantArea, higher education in Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGrantArea Context triple: [Moody Foundation, notableGrantArea, higher education in Texas]
-
A.
notableGrant
Indicates that an entity has received a grant or funding award that is considered significant or noteworthy.
-
B.
notableProjectArea
Indicates that an entity has a significant or distinguished project specifically associated with a particular area or domain.
-
C.
notableOperationArea
Indicates the geographic area or region where an entity primarily conducts or is recognized for its significant operations or activities.
-
D.
notableTargetArea
Indicates that an action, effect, or focus is specifically directed toward a particularly important or prominent area or region.
-
E.
notableWorkArea
Indicates the field or domain in which an entity’s significant work or contributions are primarily focused.
- 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_69e2458c23ec81908fa2570692c6614f |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1801358488190aa2a51f0943ea5bd |
completed | April 29, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:41 p.m.