Triple
T18432599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toll Road Investors Partnership II |
E450308
|
entity |
| Predicate | publicInterface |
P131585
|
FINISHED |
| Object | motorists using Dulles Greenway |
—
|
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: motorists using Dulles Greenway | Statement: [Toll Road Investors Partnership II, publicInterface, motorists using Dulles Greenway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicInterface Context triple: [Toll Road Investors Partnership II, publicInterface, motorists using Dulles Greenway]
-
A.
platformInterface
Indicates that one entity serves as an interface or interaction layer through which another entity accesses or communicates with a broader platform or system.
-
B.
primaryInterface
Indicates that one entity serves as the main or default interface through which another entity is accessed or interacted with.
-
C.
typicalInterface
Indicates that one entity serves as the standard or commonly used interface through which another entity is accessed or interacted with.
-
D.
usesInterface
Indicates that one entity interacts with or operates another entity through a specified interface or set of interface methods.
-
E.
designedToInterfaceWith
Indicates that one entity has been intentionally created or configured to connect, interact, or work compatibly with another entity.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51b183adc8190987bc7749d0e673c |
completed | April 19, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:27 a.m.