Triple
T9075317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sulmo |
E217468
|
entity |
| Predicate | knownAs |
P39
|
FINISHED |
| Object | Sulmoe |
E217468
|
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: Sulmoe | Statement: [Sulmo, knownAs, Sulmoe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sulmoe Context triple: [Sulmo, knownAs, Sulmoe]
-
A.
Sulmo
chosen
Sulmo is an ancient town in central Italy, historically known as the birthplace of the Roman poet Ovid.
-
B.
Mure
Mure is a Scottish surname historically associated with Lowland families and often considered a variant of or related to the name Muir.
-
C.
Camelon
Camelon is a suburban village and historic settlement located just west of Falkirk in central Scotland.
-
D.
Moate
Moate is a small town in central Ireland known for its location on the old Dublin–Galway road and its surrounding agricultural countryside.
-
E.
Sherdukpen
Sherdukpen are an indigenous ethnic group of Arunachal Pradesh in northeastern India, known for their Tibetan-influenced Buddhist traditions, distinct language, and rich festival culture.
- 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_69ca83d6c14c8190bc056d927f00a2a2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc95c53274819099b3b3047bfe8cc8 |
completed | April 1, 2026, 3:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cffdfe16c4819092c884bc3fe5daeb |
completed | April 3, 2026, 5:50 p.m. |
Created at: March 30, 2026, 7:12 p.m.