Triple

T9271874
Position Surface form Disambiguated ID Type / Status
Subject Alois E222847 entity
Predicate hasCognate P2525 FINISHED
Object Aloisio E686597 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: Aloisio | Statement: [Alois, hasCognate, Aloisio]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aloisio
Context triple: [Alois, hasCognate, Aloisio]
  • A. Aloisio chosen
    Aloisio is an Italian given name, commonly used as a variant of Aloysius and borne by various historical and contemporary figures.
  • B. Kallio
    Kallio is a Finnish surname most notably borne by Kyösti Kallio, who served as the fourth President of Finland.
  • C. Keilaniemi
    Keilaniemi is a coastal district in Espoo, Finland, known as a major business hub hosting numerous corporate headquarters and high-rise office buildings.
  • D. Särkisalo
    Särkisalo is a former coastal municipality in Southwest Finland, known for its archipelago landscape and later incorporation into the city of Salo.
  • E. Tammela
    Tammela is a rural municipality in southern Finland known for its forests, lakes, and national parks such as Torronsuo and Liesjärvi.
  • 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_69ca841ffe208190aa7bcffbef2f8379 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd07865790819099b3865a25dae58a completed April 1, 2026, 11:54 a.m.
NED1 Entity disambiguation (via context triple) batch_69d100bcd1d08190ad8fe83841f6761f completed April 4, 2026, 12:14 p.m.
Created at: March 30, 2026, 7:33 p.m.