Triple
T12701296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bundesstraße |
E303466
|
entity |
| Predicate | mayBeDowngradedTo |
P106420
|
FINISHED |
| Object | Landesstraße |
—
|
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: Landesstraße | Statement: [Bundesstraße, mayBeDowngradedTo, Landesstraße]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeDowngradedTo Context triple: [Bundesstraße, mayBeDowngradedTo, Landesstraße]
-
A.
couldBePromotedFrom
Indicates that one entity has the potential or eligibility to be advanced in status, rank, or position from another specified entity.
-
B.
partlyUpgradedTo
Indicates that an entity has undergone an incomplete or partial upgrade to another specified state, version, or configuration.
-
C.
couldBePromotedTo
Indicates a potential or eligibility for one entity to be advanced or elevated to a higher role, status, or position relative to another.
-
D.
wasUpgradedFor
Indicates that one entity was improved, enhanced, or updated specifically to serve, benefit, or be compatible with another entity.
-
E.
mayBeReplacedBy
Indicates that one entity can potentially be substituted or superseded by another entity.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d962a32c6481908ddaddae4ea267bf |
completed | April 10, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69d960be63f081908a5ef5ef17a311bf |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d96297b81c819081ad1432dc5f15f4 |
completed | April 10, 2026, 8:50 p.m. |
Created at: April 9, 2026, 5:22 p.m.