Triple
T17268942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Food for Progress |
E419201
|
entity |
| Predicate | typicalProjectDuration |
P85699
|
FINISHED |
| Object | 3 to 5 years |
—
|
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: 3 to 5 years | Statement: [Food for Progress, typicalProjectDuration, 3 to 5 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalProjectDuration Context triple: [Food for Progress, typicalProjectDuration, 3 to 5 years]
-
A.
projectLength
chosen
Indicates the duration or total time span over which a project is planned or executed.
-
B.
typicalCompletionTimeInWeeks
Indicates the usual number of weeks it takes to complete the associated task, process, or activity.
-
C.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
D.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
E.
timeToComplete
Indicates the duration required for an entity or process to be fully completed.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4803b48190894b3bb9a4970602 |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.