Triple
T1899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Science Foundation |
E35
|
entity |
| Predicate | primaryFocus |
P31
|
FINISHED |
| Object | fundamental research |
—
|
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: fundamental research | Statement: [National Science Foundation, primaryFocus, fundamental research]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFocus Context triple: [National Science Foundation, primaryFocus, fundamental research]
-
A.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
B.
focusPeriod
Indicates the specific time span during which attention, activity, or analysis is concentrated on something.
-
C.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of another entity.
-
D.
purpose
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
-
E.
presentedBy
Indicates that something (such as an event, performance, or work) is formally organized, hosted, or introduced by a particular person or 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_69a22cde80848190b62c5f556b4d62ba |
completed | Feb. 27, 2026, 11:46 p.m. |
| NER | Named-entity recognition | batch_69a2346846608190b6b40d31f1dbd685 |
completed | Feb. 28, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69a233c396ec8190986608d07fb251d4 |
completed | Feb. 28, 2026, 12:16 a.m. |
Created at: Feb. 27, 2026, 11:48 p.m.