Triple
T31061764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autoroute A1 |
E791558
|
entity |
| Predicate | servesAsRouteTowards |
P141321
|
FINISHED |
| Object | Belgium |
—
|
NE NERFINISHED |
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: Belgium | Statement: [Autoroute A1, servesAsRouteTowards, Belgium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesAsRouteTowards Context triple: [Autoroute A1, servesAsRouteTowards, Belgium]
-
A.
servesAsRouteTo
chosen
Indicates that one entity functions as a pathway, channel, or means of access leading to another entity.
-
B.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
-
C.
servesAsGatewayTo
Indicates that one entity functions as an entry point, access route, or intermediary channel that enables reaching or connecting to another entity.
-
D.
isMostCommonRouteTo
Indicates that one route is the most frequently used or typical way to reach a particular destination or outcome compared to all other possible routes.
-
E.
servesAsBaseForRoute
Indicates that one entity functions as the foundational or starting point upon which a route is defined, constructed, or planned.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69feabcda59481908f2bc13b46fcced1 |
completed | May 9, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69feaabd63f88190b30dcf6dd2ea39d1 |
completed | May 9, 2026, 3:32 a.m. |
Created at: April 29, 2026, 9:01 p.m.