Triple
T2912897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presidential Innovation Fellows program |
E63724
|
entity |
| Predicate | placementIn |
P42883
|
FINISHED |
| Object | federal agencies |
—
|
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: federal agencies | Statement: [Presidential Innovation Fellows program, placementIn, federal agencies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placementIn Context triple: [Presidential Innovation Fellows program, placementIn, federal agencies]
-
A.
positionEstablishedIn
Indicates the point in time or event when a particular position, role, or office was formally created or instituted.
-
B.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
C.
propertyLocation
Indicates the geographical place or address where a property is situated or found.
-
D.
meetsInPlaceOf
Indicates that one entity meets or comes together with another specifically at a designated place or location.
-
E.
positioning
Indicates the spatial or contextual arrangement of one entity relative to another or within a given environment.
- 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe0eb77708190b745b887f3b9a618 |
completed | March 7, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69abdd1b77608190b20fc078fdb85e64 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abddedd72c819094a9c4161af07780 |
completed | March 7, 2026, 8:12 a.m. |
Created at: March 6, 2026, 10:11 p.m.