Triple
T23185825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | stellar parallax of 61 Cygni |
E579590
|
entity |
| Predicate | angularUnit |
P12631
|
FINISHED |
| Object | arcsecond |
—
|
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: arcsecond | Statement: [stellar parallax of 61 Cygni, angularUnit, arcsecond]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: angularUnit Context triple: [stellar parallax of 61 Cygni, angularUnit, arcsecond]
-
A.
unitSystem
Indicates the system of measurement units (such as metric or imperial) that is used to quantify associated values or attributes.
-
B.
nativeUnit
Indicates that one unit is the original, inherent, or default measurement unit associated with a given quantity or entity.
-
C.
coordinateUnit
Indicates that one unit serves as a coordinate or reference unit relative to another in a measurement, spatial, or organizational context.
-
D.
unitOfMeasure
chosen
Indicates that one entity specifies the standard unit in which the quantity or value of another entity is measured.
-
E.
naturalUnitsValue
Indicates that a quantity is expressed in natural units, specifying its value when fundamental physical constants are normalized (e.g., c = ħ = k_B = 1).
- 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_69e245ff8000819090d12008805315b7 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f7230208190820acf52f537b3ff |
completed | April 29, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:05 p.m.