Triple

T13187776
Position Surface form Disambiguated ID Type / Status
Subject Funicular railway of Lyon E313903 entity
Predicate operator P179 FINISHED
Object TCL E487436 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: TCL | Statement: [Funicular railway of Lyon, operator, TCL]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TCL
Context triple: [Funicular railway of Lyon, operator, TCL]
  • A. TCL chosen
    TCL is the public transport network operator serving Lyon and its metropolitan area in France, managing buses, trams, and metro services.
  • B. TCL Corporation
    TCL Corporation is a major Chinese electronics company best known globally for manufacturing televisions and other consumer electronics.
  • C. Huawei
    Huawei is a major Chinese multinational technology company best known globally for its telecommunications equipment, smartphones, and role in 5G network infrastructure.
  • D. Midea
    Midea is an important archaeological site in Greece that was a fortified citadel of the Mycenaean civilization.
  • E. ZTE
    ZTE is a major Chinese telecommunications and technology company known for manufacturing network equipment and smartphones and competing globally with firms like Nokia and Huawei.
  • 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_69d806ae1e08819090d95bfe1538cc17 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98c4d60688190b34e65bbb5d4c152 completed April 10, 2026, 11:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6f5f7a304819081c4f51631948cbd completed May 3, 2026, 7:15 a.m.
Created at: April 9, 2026, 9:15 p.m.