Triple
T31044932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stengel GmbH |
E791096
|
entity |
| Predicate | hasFounderProfession |
P97851
|
FINISHED |
| Object | roller coaster designer |
—
|
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: roller coaster designer | Statement: [Stengel GmbH, hasFounderProfession, roller coaster designer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFounderProfession Context triple: [Stengel GmbH, hasFounderProfession, roller coaster designer]
-
A.
foundedByOccupation
Indicates that an entity (such as an organization or institution) was founded by a person or group characterized by a specific occupation or professional role.
-
B.
associatedProfessionOfFounder
chosen
Indicates the professional field or occupation linked to the founder of an entity.
-
C.
founderKnownFor
Indicates that a founder is particularly recognized or notable for a specific work, achievement, product, or contribution.
-
D.
workIncludesRoleOfFounder
Indicates that a work involves or credits an entity in the specific role of founder.
-
E.
hasFounderName
Indicates that an entity has a founder whose personal name is given by the associated value.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: April 29, 2026, 8:59 p.m.