Triple
T18956317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vela |
E463788
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | MuVelorum |
—
|
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: MuVelorum | Statement: [Vela, contains, MuVelorum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MuVelorum Context triple: [Vela, contains, MuVelorum]
-
A.
MuVelorum
chosen
Mu Velorum is a bright giant star in the southern constellation Vela, visible to the naked eye and notable as one of the constellation’s prominent members.
-
B.
Nomentum
Nomentum was an ancient town in Latium, northeast of Rome, known as a minor but historically significant settlement along important Roman roads.
-
C.
Vtek
Vtek is a music producer known for working with the Nigerian singer Empress.
-
D.
Velaro
Velaro is a family of high-speed electric multiple unit trains developed by Siemens for use on major rail networks worldwide.
-
E.
VelaX
VelaX is a pulsar wind nebula powered by the Vela pulsar, located within the Vela supernova remnant in the constellation Vela.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5cdf2d08190a0aecd3fa5335a75 |
completed | April 20, 2026, 7:29 a.m. |
Created at: April 10, 2026, noon