Triple
T16417739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaia Data Release 2 |
E398732
|
entity |
| Predicate | magnitudeRange |
P1937
|
FINISHED |
| Object | G ~ 3 to 21 |
—
|
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: G ~ 3 to 21 | Statement: [Gaia Data Release 2, magnitudeRange, G ~ 3 to 21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: magnitudeRange Context triple: [Gaia Data Release 2, magnitudeRange, G ~ 3 to 21]
-
A.
magnitudeScale
Indicates the scale or measurement system used to quantify the magnitude or intensity of something.
-
B.
magnitude
chosen
Indicates a relationship where a quantitative size, extent, or intensity is assigned to or compared between entities or values.
-
C.
altitudeRange_m
Indicates the range of altitudes, measured in meters, over which the relationship or condition holds.
-
D.
majorRangeIncludes
Indicates that a major range (such as a primary geographic or categorical span) encompasses or contains another specified range.
-
E.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328798a488190a5fad01c3c95584c |
completed | April 18, 2026, 6:45 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.