Triple
T31695881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guimard entrance from Paris Métro |
E808916
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Paris Métro entrance |
C34082
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Paris Métro entrance Context triple: [Guimard entrance from Paris Métro, instanceOf, Paris Métro entrance]
-
A.
Paris Métro station complex
A Paris Métro station complex is an interconnected set of underground (and sometimes surface) platforms, passageways, and facilities that serve multiple metro lines and transport modes within a single integrated node in the Paris transit network.
-
B.
Lyon Metro station
A Lyon Metro station is a designated public transit facility within the Lyon Metro network where passengers access, board, and transfer between metro trains.
-
C.
Paris Métro infrastructure
Paris Métro infrastructure encompasses the physical and technical systems—tracks, tunnels, stations, rolling stock, power supply, signaling, and maintenance facilities—that enable the operation of the Paris urban rapid transit network.
-
D.
Marseille Metro station
A Marseille Metro station is a designated public transit facility within the Marseille Metro network where trains stop to allow passengers to board, alight, and transfer between lines or other transport modes.
-
E.
metro station entrance
chosen
A metro station entrance is a designated access point at street level that allows passengers to enter or exit an underground or elevated metro system, typically featuring stairs, escalators, elevators, signage, and fare control access.
- F. None of above.
Provenance (1 batch)
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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:10 p.m.