Triple
T33699954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annie |
E863426
|
entity |
| Predicate | hasAuthorStyleContext |
P183736
|
FINISHED |
| Object | Ayckbourn ensemble 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: Ayckbourn ensemble comedy | Statement: [Annie, hasAuthorStyleContext, Ayckbourn ensemble comedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorStyleContext Context triple: [Annie, hasAuthorStyleContext, Ayckbourn ensemble comedy]
-
A.
hasAuthorContext
chosen
Indicates that an entity is associated with contextual information about its author, such as background, circumstances, or metadata relevant to authorship.
-
B.
hasStyle
Indicates that an entity possesses, exhibits, or is characterized by a particular style or manner.
-
C.
hasRuleStyle
Indicates that an entity is associated with a particular rule-based style or formatting specification.
-
D.
hasSystemStyle
Indicates that one entity is associated with, or characterized by, a particular system-defined style of another entity.
-
E.
hasStyleIndex
Indicates that an entity is associated with a particular style identified by a specific index or position.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 1, 2026, 1:43 a.m.