Triple
T5036764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A10 ring road of Amsterdam |
E113442
|
entity |
| Predicate | isPartOfRingRoadSystem |
P36772
|
FINISHED |
| Object | Amsterdam ring road system |
—
|
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: Amsterdam ring road system | Statement: [A10 ring road of Amsterdam, isPartOfRingRoadSystem, Amsterdam ring road system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfRingRoadSystem Context triple: [A10 ring road of Amsterdam, isPartOfRingRoadSystem, Amsterdam ring road system]
-
A.
isOnOrbitalMotorway
Indicates that one entity (typically a route or segment) lies on or forms part of an orbital motorway that encircles a city or area.
-
B.
isInnerCityRoad
Indicates that a road is located within and primarily serves the inner (central, densely built-up) area of a city.
-
C.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
D.
roadNetworkPartOf
chosen
Indicates that one road network segment or component is a constituent part of a larger road network.
-
E.
beltwayAround
Indicates that one roadway or route functions as a beltway encircling or surrounding another specified area or location.
- 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_69bd44384298819089c49e7c330ec7b8 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73bb069c8190af86f1b2f95f3d95 |
completed | March 20, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69bd71529d608190a53470ba6c14bb1d |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.