Triple
T16005631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Bus Direct |
E388209
|
entity |
| Predicate | providedConnectionBetween |
P845
|
FINISHED |
| Object | Paris Charles de Gaulle Airport and central Paris |
—
|
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: Paris Charles de Gaulle Airport and central Paris | Statement: [Le Bus Direct, providedConnectionBetween, Paris Charles de Gaulle Airport and central Paris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providedConnectionBetween Context triple: [Le Bus Direct, providedConnectionBetween, Paris Charles de Gaulle Airport and central Paris]
-
A.
connectionTo
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
-
B.
connectsTo
chosen
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
C.
partlyConnectedBy
Indicates that two entities are linked or joined by something in an incomplete, partial, or not fully continuous way.
-
D.
ridgeConnection
Indicates a structural relationship where one ridge is connected or linked to another ridge, forming a continuous or associated ridge feature.
-
E.
compatibleConnection
Indicates that two entities can be connected or used together without conflict, supporting proper operation or interaction.
- 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_69d86dabcb7c8190b6a39d6831d2fa1b |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142dc081c819082527e3fa8773460 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:55 a.m.