Triple
T21026563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M91 |
E517954
|
entity |
| Predicate | isLocatedNearOnSky |
P133149
|
FINISHED |
| Object | M100 |
—
|
NE NERFINISHED |
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: M100 | Statement: [M91, isLocatedNearOnSky, M100]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M100 Context triple: [M91, isLocatedNearOnSky, M100]
-
A.
M100
M100 is a large-displacement V8 engine developed by Mercedes-Benz in the 1960s, renowned for powering the flagship 600 limousine and offering exceptional smoothness and torque.
-
B.
M100
chosen
M100 is a bright grand-design spiral galaxy located in the constellation Coma Berenices and is one of the largest and most prominent members of the Virgo Cluster.
-
C.
M10
M10 is a major roadway designation used for important motorways or highways in several countries’ transportation networks.
-
D.
M10
M10 is a bright globular star cluster in the constellation Ophiuchus, cataloged by Charles Messier in 1764.
-
E.
M-10
M-10 is a major motorway in Russia that serves as a key route connecting Moscow and Saint Petersburg.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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. |
Created at: April 16, 2026, 1:55 p.m.