Triple
T5089215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 47 Tucanae |
E114711
|
entity |
| Predicate | isNearOnSky |
P45695
|
FINISHED |
| Object | south celestial pole |
—
|
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: south celestial pole | Statement: [47 Tucanae, isNearOnSky, south celestial pole]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNearOnSky Context triple: [47 Tucanae, isNearOnSky, south celestial pole]
-
A.
isCloseTo
chosen
Indicates that one entity is physically or conceptually near another, within a relatively short distance or range.
-
B.
hasNearbyObservatories
Indicates that one entity has one or more observatories located in close geographic proximity to it.
-
C.
hasApproximateDistanceFromEquator
Indicates that one entity has an approximate measured or estimated distance from the Earth's equator.
-
D.
closestApproachDistance
Indicates the minimum distance between two entities at the point where they come closest to each other during their motion or interaction.
-
E.
isNearbyGalaxyGroup
Indicates that one galaxy group is located at a relatively close distance to another galaxy group in astronomical terms.
- 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_69bd443e941881908eb4e8c685b6f656 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd753f6544819090c028b34ee87536 |
completed | March 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69bd715c0a448190afc837c6c31dc6ab |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.