Triple
T16005662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Bus Direct |
E388209
|
entity |
| Predicate | operatedOnInfrastructure |
P6820
|
FINISHED |
| Object | Paris road network |
—
|
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 road network | Statement: [Le Bus Direct, operatedOnInfrastructure, Paris road network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedOnInfrastructure Context triple: [Le Bus Direct, operatedOnInfrastructure, Paris road network]
-
A.
usesInfrastructure
chosen
Indicates that one entity makes use of, depends on, or operates through the infrastructure provided or managed by another entity.
-
B.
isPartOfInfrastructure
Indicates that something belongs to, is included within, or functions as a component of a larger infrastructure system.
-
C.
operatedOn
Indicates that one entity has performed a surgical or procedural operation on another entity.
-
D.
operatedWith
Indicates that an entity performed an action, function, or process using a specified tool, method, or instrument.
-
E.
parallelInfrastructure
Indicates that two or more infrastructure elements are arranged or operate in parallel to each other, typically serving similar functions simultaneously.
- 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.