Triple
T12975838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vinci SA |
E321520
|
entity |
| Predicate | hasSubsidiary |
P254
|
FINISHED |
| Object | Cofiroute |
E246941
|
NE 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: Cofiroute | Statement: [Vinci SA, hasSubsidiary, Cofiroute]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cofiroute Context triple: [Vinci SA, hasSubsidiary, Cofiroute]
-
A.
Cofiroute
chosen
Cofiroute is a French toll road concession company that finances, builds, and operates motorway and tunnel infrastructure.
-
B.
koa-router
koa-router is a popular routing middleware for the Koa web framework that provides URL routing, route parameters, and middleware composition for building Node.js APIs and web applications.
-
C.
Sharp Edge route
The Sharp Edge route is a famous, exposed scrambling ridge in England’s Lake District, known for its dramatic narrow crest and challenging ascent to the summit of Blencathra.
-
D.
Route 501
Route 501 is a numbered roadway that serves as a regional transportation corridor connected to Route 440.
-
E.
Routing
Routing is the Symfony component responsible for mapping incoming HTTP requests to specific controllers and actions based on defined URL patterns.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e48c0208190bb7ec80780480b37 |
completed | April 10, 2026, 10:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6b8ec821c81909398d8e02d69dcbf |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 9, 2026, 8:37 p.m.