Triple
T18772368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melotte 13 and Melotte 14 |
E459046
|
entity |
| Predicate | angularProximity |
P45695
|
FINISHED |
| Object | close together on the celestial sphere |
—
|
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: close together on the celestial sphere | Statement: [Melotte 13 and Melotte 14, angularProximity, close together on the celestial sphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: angularProximity Context triple: [Melotte 13 and Melotte 14, angularProximity, close together on the celestial sphere]
-
A.
isCloseTo
chosen
Indicates that one entity is physically or conceptually near another, within a relatively short distance or range.
-
B.
closestTo
Indicates that one entity is nearer in distance to a reference entity than any other comparable entity.
-
C.
angularSeparationFrom
Indicates the angular distance between two entities as measured from a common observation point.
-
D.
closerTo
Indicates that one entity is at a smaller distance to a reference entity than another entity is.
-
E.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e59336a6b08190819595a55177264e |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.