Triple
T8459507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 407 ETR Concession Company Limited |
E200005
|
entity |
| Predicate | routeTypeManaged |
P82764
|
FINISHED |
| Object | express toll route |
—
|
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: express toll route | Statement: [407 ETR Concession Company Limited, routeTypeManaged, express toll route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeTypeManaged Context triple: [407 ETR Concession Company Limited, routeTypeManaged, express toll route]
-
A.
routeRole
Indicates the specific functional role or purpose that an entity has within a particular route or path.
-
B.
routeSetting
Indicates that one entity configures or defines the path or course to be followed by another entity (such as a vehicle, signal, or data flow).
-
C.
routerTypes
Indicates that one entity specifies or categorizes the types or kinds of routers associated with another entity.
-
D.
routeMayInclude
Indicates that a given route can optionally pass through, contain, or involve a specified segment, location, or element as part of its path.
-
E.
routeVia
Indicates that a connection, path, or communication between two points is established or carried out through an intermediate location, node, or channel.
- F. None of above. chosen
Provenance (4 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe49e036c8190abb50ca272266ca6 |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe12dd0b88190a38ec4d15dcc870b |
completed | March 31, 2026, 2:58 p.m. |
Created at: March 30, 2026, 6:10 p.m.