Triple
T25492667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arts et Métiers (Paris Métro) |
E638874
|
entity |
| Predicate | line3PlatformLocation |
P158595
|
FINISHED |
| Object | under Rue Réaumur |
—
|
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: under Rue Réaumur | Statement: [Arts et Métiers (Paris Métro), line3PlatformLocation, under Rue Réaumur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: line3PlatformLocation Context triple: [Arts et Métiers (Paris Métro), line3PlatformLocation, under Rue Réaumur]
-
A.
lineAPlatformOpened
Indicates that the platform associated with line A has been opened and is now available for use.
-
B.
identifiesStationWithinLine
Indicates that a specific station is recognized as belonging to, or located within, a particular transit line.
-
C.
lightRailNetworkEndpointFor
Indicates that one entity serves as an endpoint (such as a terminus or boundary station) of a specified light rail network.
-
D.
railPosition
Indicates the relative location or alignment of something with respect to a rail or set of rails.
-
E.
line1PlatformsOpened
Indicates that the platforms serving line 1 have been opened and are available for use.
- 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_69e75dbbd2a88190b70e1e645de14b9a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f7a743d081908e290089309981bb |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 2:39 p.m.