Triple
T29768584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorado |
E753984
|
entity |
| Predicate | associatedGalaxy |
P29786
|
FINISHED |
| Object | Large Magellanic Cloud |
E20343
|
NE 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: Large Magellanic Cloud | Statement: [Dorado, associatedGalaxy, Large Magellanic Cloud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedGalaxy Context triple: [Dorado, associatedGalaxy, Large Magellanic Cloud]
-
A.
isSatelliteGalaxyOf
Indicates that one galaxy orbits and is gravitationally bound to another, larger host galaxy as its satellite.
-
B.
associatedGlobularCluster
Indicates that one entity is linked or connected to a particular globular cluster in an astronomically relevant way.
-
C.
isNearbyGalaxyOf
Indicates that one galaxy is located relatively close in space to another galaxy, within a limited cosmic distance.
-
D.
relatedAstronomicalObject
chosen
Indicates that one astronomical object has a specified relationship or association with another astronomical object.
-
E.
associatedStarCluster
Indicates that one entity is related to or grouped with a particular star cluster, such as being part of, located in, or otherwise linked to that cluster.
- F. None of above.
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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a26c8f580ec819095b3ad8647757e96 |
completed | June 8, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 8:40 p.m.