Triple
T6829779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Cirque Imaginaire |
E157106
|
entity |
| Predicate | storytellingMode |
P11858
|
FINISHED |
| Object | non-linear narrative |
—
|
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: non-linear narrative | Statement: [Le Cirque Imaginaire, storytellingMode, non-linear narrative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storytellingMode Context triple: [Le Cirque Imaginaire, storytellingMode, non-linear narrative]
-
A.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
B.
storyFunction
Indicates that one entity serves a particular narrative role or function within the story structure of another entity.
-
C.
narrativeType
chosen
Indicates the specific kind or category of narrative (e.g., genre, structural form, or storytelling mode) associated with an entity.
-
D.
narrativeStrategy
Indicates the method or approach used to structure, present, or convey a story or sequence of events.
-
E.
storyline
Indicates that one entity serves as the narrative plot or sequence of events associated with another entity.
- 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_69c6882a5b5c8190917a7db9ed36bad1 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d626df448190b4b1d7406d571d07 |
completed | March 27, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69c6d09d95f0819091ca7f897dc21efe |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.