Triple
T15623381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stay |
E375619
|
entity |
| Predicate | usedInStorytelling |
P68374
|
FINISHED |
| Object | toHighlightTurningPointInRelationship |
—
|
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: toHighlightTurningPointInRelationship | Statement: [Stay, usedInStorytelling, toHighlightTurningPointInRelationship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInStorytelling Context triple: [Stay, usedInStorytelling, toHighlightTurningPointInRelationship]
-
A.
usedInCulture
Indicates that something (such as an object, practice, or concept) is employed, referenced, or plays a role within a particular culture or cultural context.
-
B.
usedInFictionalWork
Indicates that something (such as a concept, object, or character) appears or is employed within a specific fictional work.
-
C.
modeOfTelling
Indicates the manner or medium through which something is narrated, communicated, or expressed.
-
D.
fictionalUse
Indicates that one entity makes use of another within a fictional or imaginary context, rather than in real-world usage.
-
E.
narrativeStrategy
chosen
Indicates the method or approach used to structure, present, or convey a story or sequence of events.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e9cfd94819091459aa17a002eaf |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:14 a.m.