Triple
T35811051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Räuchermann |
E1035229
|
entity |
| Predicate | smokeExitsFrom |
P184147
|
FINISHED |
| Object | mouth |
—
|
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: mouth | Statement: [Räuchermann, smokeExitsFrom, mouth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: smokeExitsFrom Context triple: [Räuchermann, smokeExitsFrom, mouth]
-
A.
smokeEvacuation
Indicates the removal or extraction of smoke from an area, typically to maintain visibility and safety.
-
B.
smokeSystem
Indicates that an entity is equipped with or associated with a smoke-generating system (e.g., for signaling, testing, or special effects).
-
C.
smokestacks
Indicates the presence or involvement of smokestacks, typically as structures emitting smoke or exhaust as part of an industrial or energy-related process.
-
D.
smokeLevel
Indicates the intensity or concentration of smoke present in or produced by an entity or environment.
-
E.
smokingLocation
Indicates the place or environment where the act of smoking occurs or is permitted.
- F. None of above. chosen
Provenance (4 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:06 p.m.