Triple

T9595981
Position Surface form Disambiguated ID Type / Status
Subject Consulta of Corsica E231531 entity
Predicate shortName P43 FINISHED
Object Consulta E125234 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: Consulta | Statement: [Consulta of Corsica, shortName, Consulta]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Consulta
Context triple: [Consulta of Corsica, shortName, Consulta]
  • A. Consulta chosen
    Consulta is the commonly used short name for Italy’s Constitutional Court, the supreme body responsible for reviewing the constitutionality of laws and resolving certain institutional disputes.
  • B. Ask
    Ask is a small village located in the municipality of Ringerike in Buskerud county, Norway.
  • C. Ask
    Ask was a rebranded version of the Ask Jeeves web search engine, offering general internet search services.
  • D. Qus
    Qus is a town in Upper Egypt situated along the Nile River within the modern Qena Governorate.
  • E. Sual
    Sual is a coastal municipality in the province of Pangasinan, Philippines, known for hosting one of the country’s major coal-fired power plants along the Lingayen Gulf.
  • 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_69ca8482884481908eccdfdf64d6fbf7 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9a164c20819093fa863f8f5f79c0 completed April 1, 2026, 10:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69d16199845881908f8a91182ca48250 completed April 4, 2026, 7:08 p.m.
Created at: March 30, 2026, 8:07 p.m.