Triple
T23586358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steyr-Münichholz subcamp |
E582354
|
entity |
| Predicate | workSiteFor |
P134061
|
FINISHED |
| Object | Steyr-Daimler-Puch AG |
—
|
NE NERFINISHED |
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: Steyr-Daimler-Puch AG | Statement: [Steyr-Münichholz subcamp, workSiteFor, Steyr-Daimler-Puch AG]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workSiteFor Context triple: [Steyr-Münichholz subcamp, workSiteFor, Steyr-Daimler-Puch AG]
-
A.
worksAtSite
chosen
Indicates that an entity performs its job or duties at a particular physical site or location.
-
B.
workAt
Indicates that an entity is employed by or performs work for a particular organization, company, or place.
-
C.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
D.
locationOfWork
Indicates the place or site where an entity performs its work or carries out its professional activities.
-
E.
workSetting
Indicates the environment, context, or conditions in which the work or activity is carried out.
- 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b03195748190b7e34f334902ac93 |
completed | April 29, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:41 p.m.