Triple

T8880088
Position Surface form Disambiguated ID Type / Status
Subject Paris Métro line 7bis E211386 entity
Predicate hasRollingStock P1305 FINISHED
Object MF 88 E735518 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: MF 88 | Statement: [Paris Métro line 7bis, hasRollingStock, MF 88]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: MF 88
Context triple: [Paris Métro line 7bis, hasRollingStock, MF 88]
  • A. MF 88 chosen
    MF 88 is a type of rubber-tyred electric multiple unit train used on the Paris Métro, notable for its experimental design and limited deployment.
  • B. MF 77
    MF 77 is a steel-wheeled electric multiple unit train used on several lines of the Paris Métro, introduced in the late 1970s to modernize the network’s rolling stock.
  • C. MF 19
    MF 19 is a planned new generation of Paris Métro rubber-tyred rolling stock intended to replace older MF-series trains on several lines.
  • D. MF 67
    MF 67 is a class of steel-wheeled electric multiple unit trains that have long served as a primary rolling stock type on the Paris Métro.
  • E. M-86
    M-86 is a state trunkline highway in southern Michigan that serves as an east–west route connecting several small communities and regional roads.
  • 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_69ca838f9e20819096ab1f236a70381a completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc61677c9c8190aa09dc2a05d4cf95 completed April 1, 2026, 12:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfabc1992481909e8a4216086d5111 completed April 3, 2026, noon
Created at: March 30, 2026, 6:52 p.m.