Triple
T9201584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hayley Sings |
E220852
|
entity |
| Predicate | hasTrackInterpretationType |
P52235
|
FINISHED |
| Object | song interpretations |
—
|
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: song interpretations | Statement: [Hayley Sings, hasTrackInterpretationType, song interpretations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrackInterpretationType Context triple: [Hayley Sings, hasTrackInterpretationType, song interpretations]
-
A.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
B.
hasInterpretiveElement
chosen
Indicates that something includes or is associated with an element involving interpretation, such as a subjective, analytical, or explanatory component.
-
C.
trackType
Indicates the specific kind or category of track associated with an entity, such as its functional or physical classification.
-
D.
hasTrackContext
Indicates that an entity is associated with or occurs within a particular track-related context (such as a specific track, route, or sequence).
-
E.
isTrackEvent
Indicates that an event is classified as a track-related occurrence, such as a specific action or interaction being recorded for tracking or analytics purposes.
- 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_69ca83e8e9248190862cf3e41693b310 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd9429b448190a078e9cdfedd4918 |
completed | April 1, 2026, 8:37 a.m. |
| PD | Predicate disambiguation | batch_69cc660af2408190ae06eb8326e1c64e |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:25 p.m.