Triple
T37235405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Die Werkself |
E923558
|
entity |
| Predicate | reflectsOrigin |
P3654
|
FINISHED |
| Object | club founded by workers of Bayer company |
—
|
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: club founded by workers of Bayer company | Statement: [Die Werkself, reflectsOrigin, club founded by workers of Bayer company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reflectsOrigin Context triple: [Die Werkself, reflectsOrigin, club founded by workers of Bayer company]
-
A.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
B.
hasOriginIn
chosen
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
C.
metaOrigin
Indicates the original source, provenance, or creation context from which the associated metadata itself is derived.
-
D.
indirectOrigin
Indicates that one entity originates from or is derived through one or more intermediate sources or processes from another entity, rather than directly.
-
E.
classOrigin
Indicates the original class or category from which an entity is derived, instantiated, or classified.
- 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_69f76ea9fee88190a589f661d95a7189 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb4134225081909fd60703b8cae397 |
completed | May 6, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69fb35bf767081908de8345358ca7f44 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.