Triple
T1886999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris Métro Line 1 |
E39985
|
entity |
| Predicate | platformScreenDoors |
P22114
|
FINISHED |
| Object | presentOnAllStations |
—
|
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: presentOnAllStations | Statement: [Paris Métro Line 1, platformScreenDoors, presentOnAllStations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformScreenDoors Context triple: [Paris Métro Line 1, platformScreenDoors, presentOnAllStations]
-
A.
hasPlatformScreenDoors
chosen
Indicates that a transit station or platform is equipped with platform screen doors separating passengers from the tracks.
-
B.
hasEndDoors
Indicates that an object or structure is equipped with doors located at one or more of its ends.
-
C.
hasDoor
Indicates that one entity possesses or is equipped with a door that provides access to or through it.
-
D.
doorConfiguration
Indicates how a door is arranged or set up in relation to its frame, opening direction, and operational characteristics.
-
E.
doorType
Indicates the specific kind or category of door associated with an entity.
- 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_69a88633e4fc8190b7eb40463e048ec5 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb121a3cc81909c60ac65627142d1 |
completed | March 7, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69abafe61bc48190ac9ead027df930e1 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.