Triple
T16566461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hipparcos |
E402473
|
entity |
| Predicate | extendedMissionDuration |
P13423
|
FINISHED |
| Object | about 3.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: about 3.5 years | Statement: [Hipparcos, extendedMissionDuration, about 3.5 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendedMissionDuration Context triple: [Hipparcos, extendedMissionDuration, about 3.5 years]
-
A.
missionExtension
Indicates that an existing mission is being prolonged beyond its originally planned duration or scope.
-
B.
missionDuration
chosen
Indicates the length of time over which a mission or operation takes place from start to finish.
-
C.
extendedIndefinitelyOn
Indicates that something was prolonged or continued without a specified end point in relation to something else.
-
D.
missionDurationType
Indicates the classification of a mission’s length or time span (e.g., short-term, long-term, extended).
-
E.
extendedFor
Indicates that something has been lengthened in duration, scope, or extent specifically for the benefit or use of another 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35772255881909f737da89bcd06b8 |
completed | April 18, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:15 a.m.