Triple
T7154410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montmartre funicular |
E166772
|
entity |
| Predicate | hasUpperStation |
P72892
|
FINISHED |
| Object | Station Haute |
—
|
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: Station Haute | Statement: [Montmartre funicular, hasUpperStation, Station Haute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpperStation Context triple: [Montmartre funicular, hasUpperStation, Station Haute]
-
A.
upperStation
chosen
Indicates that one station is positioned higher or upstream in a system or hierarchy relative to another station.
-
B.
hasUpperFloor
Indicates that one entity possesses or includes an upper floor relative to another level or reference point.
-
C.
hasEndpointStation
Indicates that something (such as a route, line, or service) has a specific station as one of its terminal endpoints.
-
D.
hasAdjacentStationOnU7
Indicates that one station is directly next to another station along the U7 line.
-
E.
hasStationHall
Indicates that one entity (typically a station) includes or is associated with a station hall area as part of its structure or facilities.
- 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7f68384819095e6aef89555442a |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1caf4e48190b47bb398a3c1554d |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:46 p.m.