Triple
T4618554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M110 |
E100924
|
entity |
| Predicate | orbitsWithin |
P2015
|
FINISHED |
| Object | halo of the Andromeda Galaxy |
—
|
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: halo of the Andromeda Galaxy | Statement: [M110, orbitsWithin, halo of the Andromeda Galaxy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitsWithin Context triple: [M110, orbitsWithin, halo of the Andromeda Galaxy]
-
A.
orbits
chosen
Indicates that one object moves in a curved, usually repetitive path around another object due to a central force such as gravity.
-
B.
coOrbitsWith
Indicates that two celestial bodies share the same or closely related orbital path around a common central object.
-
C.
orbitsCovered
Indicates that one entity completes or spans a specified number of orbital revolutions around another entity.
-
D.
totalOrbits
Indicates the total number of orbital paths or revolutions one entity completes around another within a defined system or timeframe.
-
E.
orbitedBody
Indicates that one object moves in a path around another object due to gravitational or similar orbital forces.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e247448190ad92f194cb1127c5 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.