Triple

T6388310
Position Surface form Disambiguated ID Type / Status
Subject Council of Trent E143755 entity
Predicate heldIn P2777 FINISHED
Object Trent E16617 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: Trent | Statement: [Council of Trent, heldIn, Trent]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Trent
Context triple: [Council of Trent, heldIn, Trent]
  • A. Trent chosen
    The Trent is one of the principal rivers in England, flowing through the Midlands and joining the Humber estuary before reaching the North Sea.
  • B. Son
    The Son is a major south-flowing river in central and eastern India, known as a key tributary of the Ganges and an important waterway for the regions it traverses.
  • C. Son
    Son is a Japanese surname most prominently associated with Masayoshi Son, the billionaire founder and CEO of SoftBank.
  • D. Niles
    Niles is a historic former town in California, now a district of Fremont, known for its early silent film industry and railroad heritage.
  • E. Gustavus
    Gustavus is a Latinized masculine given name historically borne by several Swedish kings and used in various European and English-speaking contexts.
  • 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_69c008dac1ec81909cef8157ccd69962 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0686b4f34819088ff07185b34e536 completed March 22, 2026, 10:08 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6388224fc8190aabd6e6d75887367 completed March 27, 2026, 7:57 a.m.
Created at: March 22, 2026, 4:34 p.m.