Triple
T19182760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HD 25940 |
E469616
|
entity |
| Predicate | distanceParsecs |
P134767
|
FINISHED |
| Object | approximately 340 |
—
|
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: approximately 340 | Statement: [HD 25940, distanceParsecs, approximately 340]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceParsecs Context triple: [HD 25940, distanceParsecs, approximately 340]
-
A.
distanceInMegaparsecs
Indicates the physical separation between two entities measured in units of megaparsecs.
-
B.
distanceFromEarth
Indicates the measured or calculated spatial separation between an entity and the planet Earth.
-
C.
distanceFromSunCategory
Indicates the qualitative category or range into which an entity’s distance from the Sun falls (e.g., very close, moderate, far).
-
D.
relativeDistanceInUranianSystem
Indicates the comparative distance between two objects within the Uranian system, typically in terms of their separation from Uranus or from each other.
-
E.
hasApproximateDistanceFromEarth
Indicates that there is an estimated or non-exact distance between an entity and Earth.
- F. None of above. chosen
Provenance (4 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f61e1c248190ba9e220c1be61ef8 |
completed | April 20, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:07 p.m.