Triple

T30111964
Position Surface form Disambiguated ID Type / Status
Subject Paris Métro Line 7bis E765300 entity
Predicate hasLoopOrBranch P191354 FINISHED
Object secondary branch of Line 7 LITERAL 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: secondary branch of Line 7 | Statement: [Paris Métro Line 7bis, hasLoopOrBranch, secondary branch of Line 7]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLoopOrBranch
Context triple: [Paris Métro Line 7bis, hasLoopOrBranch, secondary branch of Line 7]
  • A. hasPassingLoopAt
    Indicates that a railway line or track segment includes a passing loop located at a specified place or point.
  • B. hasLoopOption
    Indicates that an entity provides or supports an option to repeat or loop an associated process, action, or sequence.
  • C. hasLoopNumber
    Indicates that an entity is associated with a specific loop identifier or count, typically representing its position or iteration within a repeated cycle or process.
  • D. hasBranchLinePurpose
    Indicates that a branch line is associated with a specific intended function or purpose within a larger network or system.
  • E. hasLoopConfiguration
    Indicates that an entity is associated with a specific loop setup or arrangement that defines how a loop operates or is structured.
  • F. None of above. chosen

Provenance (4 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_69f22475ad7c8190be7f9541044a0bbb completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fcdf2394748190b35cead3e208447d completed May 7, 2026, 6:51 p.m.
PD Predicate disambiguation batch_69fcdbe344ec8190a0471911952f4b82 completed May 7, 2026, 6:37 p.m.
PDg Predicate description generation batch_69fcdf22ab8881908b257f16522920c5 completed May 7, 2026, 6:51 p.m.
Created at: April 29, 2026, 7:10 p.m.