Triple
T16336360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaia Data Release 1 |
E396687
|
entity |
| Predicate | approximateObservationDuration |
P4874
|
FINISHED |
| Object | 14 months |
—
|
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: 14 months | Statement: [Gaia Data Release 1, approximateObservationDuration, 14 months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateObservationDuration Context triple: [Gaia Data Release 1, approximateObservationDuration, 14 months]
-
A.
hasApproximateDuration
chosen
Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
-
B.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
C.
timePeriodApproximation
Indicates that the associated time period is an estimate or approximation rather than an exact, precise value.
-
D.
eraDuration
Indicates the length of time that a particular era or period spans.
-
E.
banDurationApproximate
Indicates that the duration of a ban is known only approximately rather than as an exact, precise time period.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4e3af7881908a3116c41ed69115 |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.