Triple

T31378902
Position Surface form Disambiguated ID Type / Status
Subject Créteil–L’Échat station E800389 entity
Predicate hasExtensionProject P181678 FINISHED
Object future connection to Paris Métro Line 15 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: future connection to Paris Métro Line 15 | Statement: [Créteil–L’Échat station, hasExtensionProject, future connection to Paris Métro Line 15]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasExtensionProject
Context triple: [Créteil–L’Échat station, hasExtensionProject, future connection to Paris Métro Line 15]
  • A. hasExtensionBy
    Indicates that one entity is extended, augmented, or further developed by another entity.
  • B. hasExtensionActivity
    Indicates that an entity is associated with an additional, supplementary, or follow-up activity extending beyond its primary or core action.
  • C. hasExtensionsDirectory
    Indicates that an entity is associated with or configured to use a specific directory where its extensions or add-ons are stored.
  • D. hasExtensionBuilding
    Indicates that a primary building is associated with an additional or auxiliary extension building.
  • E. hasProjectFileExtension
    Indicates that a project is associated with or saved using a specific file extension.
  • 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_69f224e84da08190abfc2f17494a33c8 completed April 29, 2026, 3:34 p.m.
NER Named-entity recognition batch_69f7805ce6208190ac6dbd9c97989978 completed May 3, 2026, 5:05 p.m.
PD Predicate disambiguation batch_69f77956ec648190ba4fb7e9d83fd107 completed May 3, 2026, 4:35 p.m.
PDg Predicate description generation batch_69f7805c25dc8190b9977c561ba15975 completed May 3, 2026, 5:05 p.m.
Created at: April 29, 2026, 9:18 p.m.