Triple
T1840826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Large Magellanic Cloud |
E41172
|
entity |
| Predicate | isNearest |
P350
|
FINISHED |
| Object | one of the nearest galaxies to the Milky Way |
—
|
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: one of the nearest galaxies to the Milky Way | Statement: [Large Magellanic Cloud, isNearest, one of the nearest galaxies to the Milky Way]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNearest Context triple: [Large Magellanic Cloud, isNearest, one of the nearest galaxies to the Milky Way]
-
A.
closerTo
Indicates that one entity is at a smaller distance to a reference entity than another entity is.
-
B.
near
chosen
Indicates that one entity is located at a short distance from another entity in space or position.
-
C.
occursNear
Indicates that one event or entity takes place or exists in close spatial proximity to another.
-
D.
isAdjacentTo
Indicates that one entity is directly next to or bordering another without anything of the same type in between.
-
E.
hasNearbyMode
Indicates that one entity has another entity located close enough to be considered in its immediate vicinity or surrounding area.
- 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_69a88647f9388190909bc36e795bdaec |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdb0d2c8190a67f584e67979fa3 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.