Triple
T31340485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hot Gates |
E799290
|
entity |
| Predicate | hasModernRoad |
P128065
|
FINISHED |
| Object | Greek National Road 1 |
—
|
NE NERFINISHED |
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: Greek National Road 1 | Statement: [Hot Gates, hasModernRoad, Greek National Road 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernRoad Context triple: [Hot Gates, hasModernRoad, Greek National Road 1]
-
A.
hasRoadStandard
Indicates that a road or roadway segment conforms to, or is governed by, a specific road design, construction, or operational standard.
-
B.
hasRoads
Indicates that there exist constructed road connections linking the related entities.
-
C.
hasRoadCar
Indicates that one entity possesses, is associated with, or includes a road-capable car as part of its attributes or components.
-
D.
hasPermanentRoads
chosen
Indicates that an entity possesses roads that are constructed to be durable and remain in place over an extended period, rather than being temporary or seasonal.
-
E.
hasRoadComponent
Indicates that something includes, contains, or is composed of a specific road-related part or element.
- 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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: April 29, 2026, 9:16 p.m.