Triple
T4531736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messier 20 |
E106312
|
entity |
| Predicate | catalogCode |
P8090
|
FINISHED |
| Object | M20 |
E450594
|
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: M20 | Statement: [Messier 20, catalogCode, M20]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M20 Context triple: [Messier 20, catalogCode, M20]
-
A.
M20
M20 is a major motorway in South East England connecting London to the Channel Tunnel and the port of Dover.
-
B.
M20
chosen
M20 is the Trifid Nebula, a bright and picturesque star-forming emission and reflection nebula located in the constellation Sagittarius.
-
C.
M2
M2 is a major British motorway that connects London with the port town of Dover in Kent, serving as an important route to the Channel ports.
-
D.
M2
M2 is the second line of the Warsaw Metro, running east–west across the city and connecting key districts on both sides of the Vistula River.
-
E.
M2
M2 is one of the main lines of the Copenhagen Metro, connecting central Copenhagen with key districts and the airport.
- 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_69bd43f3d6e08190a91824f833d51bbe |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd579d7a88819083eb0620ca176f2e |
completed | March 20, 2026, 2:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bdb9130b3c8190b511fa8a6ac0549b |
completed | March 20, 2026, 9:16 p.m. |
Created at: March 20, 2026, 1:03 p.m.