Triple
T31592194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A2 Süd Autobahn |
E806127
|
entity |
| Predicate | hasCarinthianSection |
P197484
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [A2 Süd Autobahn, hasCarinthianSection, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCarinthianSection Context triple: [A2 Süd Autobahn, hasCarinthianSection, yes]
-
A.
hasLowerAustrianSection
Indicates that something includes, is associated with, or falls under a specific section or subdivision located in Lower Austria.
-
B.
hasBurgenlandSection
Indicates that something includes or is associated with a specific section related to Burgenland.
-
C.
hasCanton
Indicates that an entity is administratively divided into, or associated with, a specific canton.
-
D.
usesCanton
Indicates that one entity employs or applies a specific canton (administrative region or heraldic area) in its structure, context, or operations.
-
E.
includesCanton
Indicates that a larger administrative or geographic entity contains or encompasses a specific canton within its boundaries.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
| PDg | Predicate description generation | batch_69fe96c0b760819093737292d33df165 |
completed | May 9, 2026, 2:06 a.m. |
Created at: April 30, 2026, 10:28 p.m.