Triple
T31592197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A2 Süd Autobahn |
E806127
|
entity |
| Predicate | hasLowerAustrianSection |
P195096
|
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, hasLowerAustrianSection, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLowerAustrianSection Context triple: [A2 Süd Autobahn, hasLowerAustrianSection, yes]
-
A.
hasBurgenlandSection
Indicates that something includes or is associated with a specific section related to Burgenland.
-
B.
languageOnAustrianSide
Indicates that a particular language is used or present on the Austrian side of a border, context, or interaction.
-
C.
isInBundesland
Indicates that one entity (typically a place or city) is located within a specific German federal state (Bundesland).
-
D.
AustrianDesignation
Indicates that an entity has an official designation, title, or status specifically within the Austrian context (e.g., by Austrian law, administration, or standards).
-
E.
AustrianStrength
Indicates a relationship where an entity possesses or exhibits strength specifically associated with Austria, such as Austrian power, influence, or capability.
- 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_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
| PDg | Predicate description generation | batch_69fda4fe67a08190bdaa84ceabd6de6c |
completed | May 8, 2026, 8:55 a.m. |
Created at: April 30, 2026, 10:28 p.m.