Triple

T33899069
Position Surface form Disambiguated ID Type / Status
Subject Créteil–L’Échat E868995 entity
Predicate lineExtensionBeyond P82106 FINISHED
Object central Paris 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: central Paris | Statement: [Créteil–L’Échat, lineExtensionBeyond, central Paris]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: lineExtensionBeyond
Context triple: [Créteil–L’Échat, lineExtensionBeyond, central Paris]
  • A. lineExtendedTo chosen
    Indicates that one line is formed by extending another line beyond its original endpoint.
  • B. lineExtensionContext
    Indicates the broader situational or conversational context in which a particular line (such as a text line, code line, or dialogue line) is extended or continued.
  • C. lineExtensionHistory
    Indicates a historical record of changes, additions, or modifications made to a particular line over time.
  • D. lineOpeningExtension
    Indicates that a line (such as a transit or service line) is being extended beyond its original endpoint, adding new segments or stops to its route.
  • E. lineElement
    Indicates a relationship where something functions as, or is identified as, an element or segment of a line within a larger linear structure or representation.
  • F. None of above.

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_69f34997703c8190866b1d404bce531f completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f7051ad6e4819095e82bbd64761803 completed May 3, 2026, 8:19 a.m.
PD Predicate disambiguation batch_69f700fe24e08190998e2c96fbaaad38 completed May 3, 2026, 8:02 a.m.
Created at: May 1, 2026, 1:48 a.m.