Triple
T6016000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virgo Supercluster |
E133950
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | M86 |
E517947
|
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: M86 | Statement: [Virgo Supercluster, contains, M86]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M86 Context triple: [Virgo Supercluster, contains, M86]
-
A.
M86
chosen
M86 is a giant elliptical galaxy in the constellation Virgo and one of the prominent members of the Virgo Cluster.
-
B.
M84
M84 is a massive lenticular galaxy in the constellation Virgo, notable as one of the bright members of the Virgo Cluster and a target in the Messier catalog.
-
C.
M67
M67 is a short motorway in Greater Manchester, England, connecting the M60 near Denton towards Hyde and intended as the first section of an unrealized trans-Pennine route.
-
D.
M89
M89 is an elliptical galaxy in the constellation Virgo, notable as one of the bright members of the Virgo Cluster.
-
E.
M-68
M-68 is a state trunkline highway in northern Michigan that serves as an east–west route across parts of the northern Lower Peninsula.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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. |
| NED1 | Entity disambiguation (via context triple) | batch_69c108b2f09081908e94f1932aad6e58 |
completed | March 23, 2026, 9:32 a.m. |
Created at: March 22, 2026, 4:06 p.m.