Triple
T19925552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messier 80 |
E478912
|
entity |
| Predicate | locatedBetween |
P1262
|
FINISHED |
| Object | Antares |
—
|
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: Antares | Statement: [Messier 80, locatedBetween, Antares]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Antares Context triple: [Messier 80, locatedBetween, Antares]
-
A.
Antares
Antares was the Lunar Module used in NASA’s Apollo 14 mission to land astronauts on the Moon in 1971.
-
B.
Antares
chosen
Antares is a bright red supergiant star, one of the largest and most luminous visible to the naked eye, located in the constellation Scorpius.
-
C.
Antares
Antares is a medium-lift orbital launch vehicle developed primarily by Northrop Grumman to deliver cargo missions to the International Space Station and other low Earth orbit payloads.
-
D.
Orion
Orion is a coastal municipality in the province of Bataan in the Philippines, known for its historical significance and proximity to Manila Bay.
-
E.
Orion
Orion is a privacy-focused transaction manager for Ethereum-based networks, enabling confidential smart contract and enterprise blockchain operations.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659c992fc8190bd262d528be0e636 |
completed | April 20, 2026, 4:52 p.m. |
Created at: April 10, 2026, 1:53 p.m.