Triple
T32368023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bundesautobahn 7 |
E827048
|
entity |
| Predicate | hasWideningProjects |
P179959
|
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: [Bundesautobahn 7, hasWideningProjects, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWideningProjects Context triple: [Bundesautobahn 7, hasWideningProjects, yes]
-
A.
hasProjectIn
Indicates that an entity is involved with or associated with a project that takes place within a specified location or context.
-
B.
hasSubproject
Indicates that a project includes another project as a subordinate or component part within its overall structure.
-
C.
hasProject
Indicates that an entity is associated with or responsible for a particular project.
-
D.
hasNearbyProject
Indicates that one entity has a project located within a close or specified proximity to another entity or reference point.
-
E.
isSisterProjectOf
Indicates that two projects are related and aligned in purpose or scope, typically operating in parallel under a common umbrella or organization.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
| PDg | Predicate description generation | batch_69f72920c6208190aa4aba6cb6193109 |
completed | May 3, 2026, 10:53 a.m. |
Created at: May 1, 2026, 12:50 a.m.