Triple
T33814439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leo |
E866631
|
entity |
| Predicate | workStyleContext |
P47713
|
FINISHED |
| Object | sophisticated comedy |
—
|
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: sophisticated comedy | Statement: [Leo, workStyleContext, sophisticated comedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workStyleContext Context triple: [Leo, workStyleContext, sophisticated comedy]
-
A.
hasWorkStyle
chosen
Indicates the type or manner in which an entity typically performs work or carries out tasks.
-
B.
workMode
Indicates the manner, configuration, or operational state in which an entity performs its work or function.
-
C.
workWithin
Indicates that one entity performs its activities or duties inside the boundaries, scope, or context defined by another entity.
-
D.
workScope
Indicates the defined range, extent, and boundaries of tasks or responsibilities involved in a particular work activity or project.
-
E.
workAttributedContext
Indicates that a work is associated with or derived from a particular contextual source, setting, or circumstance that informs its creation or interpretation.
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 1, 2026, 1:46 a.m.