Triple
T27464310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mulsanne Straight |
E693133
|
entity |
| Predicate | trafficTypeOutsideRaces |
P146573
|
FINISHED |
| Object | two-way public road traffic |
—
|
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: two-way public road traffic | Statement: [Mulsanne Straight, trafficTypeOutsideRaces, two-way public road traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trafficTypeOutsideRaces Context triple: [Mulsanne Straight, trafficTypeOutsideRaces, two-way public road traffic]
-
A.
trafficUseOutsideEvents
Indicates that the traffic-related resource or arrangement is used during times when no special events are taking place.
-
B.
alsoRacesOutsideCountry
Indicates that an entity participates in races held outside its primary or home country.
-
C.
coversTrafficType
chosen
Indicates that one entity includes, handles, or applies to a specified type or category of traffic.
-
D.
trafficType
Indicates the category or nature of traffic involved in a given interaction, flow, or connection (e.g., type of network, data, or transport traffic).
-
E.
roadUse
Indicates that an entity utilizes or travels on a particular road or roadway for movement or transport.
- 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62dfbe6508190a6871084c5afe20f |
completed | May 2, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:51 p.m.