Triple
T10376769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argo program |
E244526
|
entity |
| Predicate | typicalFloatLifetime |
P23051
|
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: [Argo program, typicalFloatLifetime, 3 to 5 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFloatLifetime Context triple: [Argo program, typicalFloatLifetime, 3 to 5 years]
-
A.
hasMeanLifetime
chosen
Indicates the characteristic average time duration for which an entity, state, or condition persists before it decays, ends, or changes.
-
B.
lifespanType
Indicates the type or category of lifespan associated with an entity, such as whether it is finite, indefinite, or of a particular defined duration.
-
C.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
D.
typicalMaximumAge
Indicates the usual upper age limit that an entity is expected or allowed to reach under normal conditions.
-
E.
typicalRuntimeRange
Indicates the usual lower and upper bounds of time typically required for an entity to run or complete its operation.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e98278e08190a4d3ff88b4039e49 |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dface5508190a7b42f01ad0a19a2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:02 p.m.