Triple
T1900465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pompey the Great |
E37677
|
entity |
| Predicate | honorificTitle |
P2097
|
FINISHED |
| Object | Magnus |
E212509
|
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: Magnus | Statement: [Pompey the Great, honorificTitle, Magnus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Magnus Context triple: [Pompey the Great, honorificTitle, Magnus]
-
A.
Magnus
chosen
Magnus is the honorific cognomen meaning "the Great," famously borne by the Roman general and statesman Pompey.
-
B.
Magus
Magus is a mysterious spiritual master in Paulo Coelho’s novel "Brida," guiding the protagonist through her journey of self-discovery and magical initiation.
-
C.
Rigmor
Rigmor is a feminine given name of Scandinavian origin, particularly used in Norway and Denmark.
-
D.
Ragnar
Ragnar is a masculine given name of Old Norse origin, historically associated with Viking-age Scandinavia and later borne by various notable figures.
-
E.
Jarl
Jarl is a masculine given name of Scandinavian origin, historically associated with nobility and leadership.
- 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_69a8861be7148190a680937ec451a304 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb18c46c88190b10c05bf5c6a2d9c |
completed | March 7, 2026, 5:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adf3d0d01c8190ae0c8029fead4008 |
completed | March 8, 2026, 10:10 p.m. |
Created at: March 4, 2026, 7:35 p.m.