Triple
T21026556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M91 |
E517954
|
entity |
| Predicate | orbitsCenterOf |
P60183
|
FINISHED |
| Object | Local Supercluster mass distribution |
—
|
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: Local Supercluster mass distribution | Statement: [M91, orbitsCenterOf, Local Supercluster mass distribution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitsCenterOf Context triple: [M91, orbitsCenterOf, Local Supercluster mass distribution]
-
A.
orbitsBarycenterOf
chosen
Indicates that one object follows an orbital path around the shared center of mass (barycenter) of another system or group of objects.
-
B.
orbits
Indicates that one object moves in a curved, usually repetitive path around another object due to a central force such as gravity.
-
C.
coOrbitsWith
Indicates that two celestial bodies share the same or closely related orbital path around a common central object.
-
D.
orbitedBody
Indicates that one object moves in a path around another object due to gravitational or similar orbital forces.
-
E.
centerOfOrigin
Indicates the place or region where something (such as a species, product, idea, or movement) originally began or was first developed.
- 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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc7c262c8190bceb8fd26be76983 |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:55 p.m.