Triple
T10489066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deneb Algedi |
E247365
|
entity |
| Predicate | hasEquatorialCoordinates |
P24827
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Deneb Algedi, hasEquatorialCoordinates, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEquatorialCoordinates Context triple: [Deneb Algedi, hasEquatorialCoordinates, true]
-
A.
equatorialCoordinateSystem
chosen
Indicates a relationship where an object's position is specified using the equatorial coordinate system, typically defined by right ascension and declination relative to the celestial equator.
-
B.
hasGalacticCoordinateSystem
Indicates that something is associated with or defined within a particular galactic coordinate system.
-
C.
hasEquatorialRadius
Indicates that an entity has a specified radius measured at its equator.
-
D.
equatorialCoordinateEpoch
Indicates the specific reference date or epoch at which an object's equatorial coordinates (right ascension and declination) are defined or valid.
-
E.
hasApproximateDistanceFromEquator
Indicates that one entity has an approximate measured or estimated distance from the Earth's equator.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5097ca5c081908b47a08ca7885650 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8a30848190b33cf43f005a028e |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:23 p.m.