Triple
T34189806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Werner Schwab |
E877068
|
entity |
| Predicate | hasWorkCycle |
P71429
|
FINISHED |
| Object | Faekaldramen (fecal dramas) |
—
|
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: Faekaldramen (fecal dramas) | Statement: [Werner Schwab, hasWorkCycle, Faekaldramen (fecal dramas)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkCycle Context triple: [Werner Schwab, hasWorkCycle, Faekaldramen (fecal dramas)]
-
A.
hasWorkPeriod
Indicates that an entity is associated with a specific span of time during which it performs or is engaged in some work or activity.
-
B.
hasWorkOn
Indicates that one entity is associated with, contributes to, or performs work on another entity (such as a project, task, or artifact).
-
C.
hasWorkPart
Indicates that one work is a component, section, or constituent part of another, larger work.
-
D.
hasWorkCount
Indicates the number of works (such as items, creations, or outputs) associated with a given entity.
-
E.
hasActivityCycle
chosen
Indicates that an entity exhibits a recurring pattern or cycle of activity over time.
- 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_69f349af20a4819089ac24d28f2d8112 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
Created at: May 1, 2026, 1:55 a.m.