Triple
T9762385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remember Me (Coco song) |
E236699
|
entity |
| Predicate | diegeticUse |
P61040
|
FINISHED |
| Object | lullaby sung within the story |
—
|
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: lullaby sung within the story | Statement: [Remember Me (Coco song), diegeticUse, lullaby sung within the story]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diegeticUse Context triple: [Remember Me (Coco song), diegeticUse, lullaby sung within the story]
-
A.
diegeticStatus
chosen
Indicates the relationship between an element and the narrative world, specifying whether it exists within the story’s reality (perceivable by characters) or outside it (only for the audience).
-
B.
usesSampleOfSpeechBy
Indicates that one entity employs or incorporates a sample of speech produced by another entity.
-
C.
usesAudioFrom
Indicates that one entity incorporates or relies on the audio content produced or provided by another entity.
-
D.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
E.
definesUseOf
Indicates that one entity specifies or determines how another entity is to be used or applied.
- 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_69ca84d64f6c8190a4ed4e9f5936eda5 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda04c70108190a8ed09eb6f2a124e |
completed | April 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69cd03d0772c8190bd1750cf1cfba309 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:25 p.m.