Triple
T16621689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaia Data Release 3 |
E403847
|
entity |
| Predicate | timeCoverageDuration |
P75971
|
FINISHED |
| Object | 34 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: 34 months | Statement: [Gaia Data Release 3, timeCoverageDuration, 34 months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeCoverageDuration Context triple: [Gaia Data Release 3, timeCoverageDuration, 34 months]
-
A.
timeHorizonCovered
Indicates the span or duration of time that is encompassed or addressed by something (such as a plan, forecast, or agreement).
-
B.
timePeriodCoveredTo
Indicates the span or duration of time that is encompassed, addressed, or relevant to a given subject or entity.
-
C.
timeIntervalLength
chosen
Indicates the duration or length of a specified time interval.
-
D.
durationTotal
Indicates the overall length of time for which an event, process, or state persists, typically aggregating all its constituent durations.
-
E.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3754e80ec8190b3c66b33dbc7463c |
completed | April 18, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.