Triple
T19265336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Insight Grant |
E481759
|
entity |
| Predicate | supportsProjectDuration |
P85699
|
FINISHED |
| Object | long-term research projects |
—
|
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: long-term research projects | Statement: [Insight Grant, supportsProjectDuration, long-term research projects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsProjectDuration Context triple: [Insight Grant, supportsProjectDuration, long-term research projects]
-
A.
supportsProject
Indicates that one entity provides assistance, resources, or endorsement to help another entity’s project succeed.
-
B.
supportsTestDuration
Indicates that one entity is capable of handling, accommodating, or being compatible with a specified duration for a test or testing process.
-
C.
possibleDuration
Indicates the range or specific length of time that an action, event, or state can last or is allowed to last.
-
D.
projectLength
chosen
Indicates the duration or total time span over which a project is planned or executed.
-
E.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8ca2e88190baad3b6c199ee036 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:29 p.m.