Triple
T6016031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virgo Supercluster |
E133950
|
entity |
| Predicate | gravitationalCenter |
P57013
|
FINISHED |
| Object | near Virgo Cluster |
—
|
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: near Virgo Cluster | Statement: [Virgo Supercluster, gravitationalCenter, near Virgo Cluster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gravitationalCenter Context triple: [Virgo Supercluster, gravitationalCenter, near Virgo Cluster]
-
A.
centerOfMassLocation
chosen
Indicates the spatial position at which the total mass of an object or system can be considered to be concentrated.
-
B.
geographicCenter
Indicates the location that serves as the central point of a geographic area or region.
-
C.
centerOfOrigin
Indicates the place or region where something (such as a species, product, idea, or movement) originally began or was first developed.
-
D.
orbitsBarycenterOf
Indicates that one object follows an orbital path around the shared center of mass (barycenter) of another system or group of objects.
-
E.
distanceFromEarthCenter
Indicates the measured or calculated spatial distance between an entity and the center of the Earth.
- 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_69c0087361a48190905c6b55969852b8 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f82dd688190ad8882d8fb547cb5 |
completed | March 22, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69c049e75b3881908be106fbcf8c68d4 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.