Triple
T17070371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carrefour Pleyel |
E414199
|
entity |
| Predicate | isBusyStationOn |
P30882
|
FINISHED |
| Object | Line 13 |
—
|
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: Line 13 | Statement: [Carrefour Pleyel, isBusyStationOn, Line 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBusyStationOn Context triple: [Carrefour Pleyel, isBusyStationOn, Line 13]
-
A.
isBusyHub
Indicates that a location or node functions as a central point of activity with a high volume of interactions, traffic, or connections.
-
B.
isBusiestStationIn
Indicates that a station has the highest level of activity (e.g., passenger or traffic volume) within a specified area or system.
-
C.
isMajorStationOn
chosen
Indicates that a station serves as a primary or significant stop on a particular route or line.
-
D.
isBusyLine
Indicates that a communication line or channel is currently in use and cannot accept additional connections or calls.
-
E.
isOn
Indicates that one entity is physically positioned above and in contact with the top surface of another 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc0982c8190916f9905ddb5e575 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.