Triple

T21583907
Position Surface form Disambiguated ID Type / Status
Subject M6 E532592 entity
Predicate satelliteService P19767 FINISHED
Object Fransat NE NERFINISHED

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: Fransat | Statement: [M6, satelliteService, Fransat]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fransat
Context triple: [M6, satelliteService, Fransat]
  • A. Fransat chosen
    Fransat is a French free-to-air satellite television platform that provides access to the national digital terrestrial TV channels across France.
  • B. Frant
    Frant is a village and civil parish in East Sussex, England, known for its historic church, traditional village green, and rural Wealden countryside setting.
  • C. Franca
    Franca is a city in the northeastern part of the Brazilian state of São Paulo, known historically for its leather and footwear industry.
  • D. Franci
    Franci is a diminutive form of the Italian given name Francesca, often used as an affectionate nickname.
  • E. Franuś
    Franuś is a Polish diminutive form of the male given name Franciszek, used as an affectionate or familiar nickname.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c4618bec8190bcb0feb74568cbb1 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69eeeb5f2cc0819095552de70eb2ad8d completed April 27, 2026, 4:51 a.m.
Created at: April 16, 2026, 6:31 p.m.