Triple
T15512916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donauwörth |
E368758
|
entity |
| Predicate | hostsCompanySite |
P9342
|
FINISHED |
| Object | Airbus Helicopters Germany headquarters |
—
|
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: Airbus Helicopters Germany headquarters | Statement: [Donauwörth, hostsCompanySite, Airbus Helicopters Germany headquarters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostsCompanySite Context triple: [Donauwörth, hostsCompanySite, Airbus Helicopters Germany headquarters]
-
A.
hostsCompany
chosen
Indicates that one entity provides space, infrastructure, or support for a company to operate, be located, or hold activities.
-
B.
homeCompany
Indicates that one entity serves as the primary or base company associated with another entity, such as a person or subsidiary.
-
C.
siteName
Indicates the name or designated title of a particular site or location associated with an entity.
-
D.
hostsPartOf
Indicates that one entity serves as the hosting environment or container for a specific part or component of another entity.
-
E.
site
Indicates that one entity is the physical or virtual location where another entity is situated, occurs, or is based.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e04030c0208190a1931ea130075603 |
completed | April 16, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 4:01 a.m.