Triple
T38001420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lescheret |
E948110
|
entity |
| Predicate | roadAccessCountryCode |
P52349
|
FINISHED |
| Object | BE |
—
|
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: BE | Statement: [Lescheret, roadAccessCountryCode, BE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadAccessCountryCode Context triple: [Lescheret, roadAccessCountryCode, BE]
-
A.
roadAccessCountryNetwork
Indicates that there exists a road-based transportation connection or accessibility between a country and a broader network of locations or routes.
-
B.
roadNetworkCountryCode
chosen
Indicates the country code associated with the road network in which the related entity or segment is located.
-
C.
roadAccessArea
Indicates that an area is designated for or provides access to a road, such as for entry, exit, or connection.
-
D.
roadAccessFrom
Indicates that one location can be reached from another via a usable road connection.
-
E.
roadAccessDetail
Indicates details about how a location is accessed by road, such as the type, quality, or characteristics of the connecting roadway.
- 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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.