Triple
T20244770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italo Mus |
E498393
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Mus |
—
|
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: Mus | Statement: [Italo Mus, familyName, Mus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mus Context triple: [Italo Mus, familyName, Mus]
-
A.
Mus
chosen
Mus is the cognomen of the Roman family line to which the consul Publius Decius Mus of 279 BCE belonged, associated with a notable lineage of Republican military leaders.
-
B.
Mir
Mir was a Soviet and later Russian modular space station that served as a long-term research outpost in low Earth orbit from 1986 to 2001.
-
C.
Mir
Mir is a traditional South Asian noble title historically used by rulers and aristocrats, particularly in regions such as Sindh under dynasties like the Talpurs.
-
D.
Mir
Mir is a historic town in present-day Belarus, known for its multicultural heritage and the UNESCO-listed Mir Castle Complex.
-
E.
Mul
Mul is a town in Maharashtra, India, known as a local commercial and administrative center within Chandrapur district.
- 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e673a10ab48190a408a5d2c2b0808b |
completed | April 20, 2026, 6:42 p.m. |
Created at: April 11, 2026, 11:40 p.m.