Triple

T3758657
Position Surface form Disambiguated ID Type / Status
Subject Tunis Metro E82109 entity
Predicate owner P347 FINISHED
Object Transtu E386961 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: Transtu | Statement: [Tunis Metro, owner, Transtu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Transtu
Context triple: [Tunis Metro, owner, Transtu]
  • A. Transtu chosen
    Transtu is the public transport authority in Tunis responsible for operating the city’s metro and other urban transit services.
  • B. Transy
    Transy is the commonly used nickname for Transylvania University, a private liberal arts college in Lexington, Kentucky.
  • C. Trasianka
    Trasianka is a mixed East Slavic speech variety, primarily combining elements of Belarusian and Russian, commonly used in informal communication in Belarus.
  • D. Troinex
    Troinex is a small municipality in the canton of Geneva in southwestern Switzerland, situated near the French border.
  • E. Tiel
    Tiel is a historic Dutch city situated along the River Waal, known for its fruit cultivation and role as a regional trade center in the province of Gelderland.
  • 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_69ad8b1db40081908b61ffa6b78afd4d completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69adcbc20b20819095fedf803aadc53a completed March 8, 2026, 7:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4f0321c4c8190ba372148c483c4ca completed March 14, 2026, 5:20 a.m.
Created at: March 8, 2026, 3:35 p.m.