Triple
T13868953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unknown Mortal Orchestra |
E333400
|
entity |
| Predicate | notableWork |
P4
|
FINISHED |
| Object | II |
E356585
|
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: II | Statement: [Unknown Mortal Orchestra, notableWork, II]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: II Context triple: [Unknown Mortal Orchestra, notableWork, II]
-
A.
II
II is the Roman numeral used to denote the second installment in a series, such as the second episode of the Star Wars prequel trilogy.
-
B.
II
II is an IUCN protected area category designating national parks managed mainly for ecosystem protection and recreation.
-
C.
II
chosen
II is an R&B music release by American singer-songwriter Lucky Daye, showcasing his modern soul sound and songwriting.
-
D.
III
III is the regnal number designating Henry III, a powerful 11th-century Holy Roman Emperor known for consolidating imperial authority and influencing church reform.
-
E.
III
III is the regnal number designating Friedrich III, Elector of Saxony, a key early supporter and protector of Martin Luther during the Protestant Reformation.
- 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_69d81c5ced9c8190b0e9bcc6effe5959 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de05c530148190b11704300bbd5f9b |
completed | April 14, 2026, 9:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7c105da548190b908a54fec029236 |
completed | May 3, 2026, 9:41 p.m. |
Created at: April 9, 2026, 10:14 p.m.