Triple
T32674604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sing My Songs to Me |
E835396
|
entity |
| Predicate | hasSegueInto |
P144022
|
FINISHED |
| Object | For Everyman (song) |
—
|
NE NERFINISHED |
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: For Everyman (song) | Statement: [Sing My Songs to Me, hasSegueInto, For Everyman (song)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSegueInto Context triple: [Sing My Songs to Me, hasSegueInto, For Everyman (song)]
-
A.
hasSubsequent
Indicates that one entity occurs, appears, or is positioned after another in a defined sequence or order.
-
B.
continuesInto
chosen
Indicates that one entity extends forward in time, space, or sequence so that it directly proceeds into and forms a continuous progression with another entity.
-
C.
hasSegmentOn
Indicates that one entity includes or occupies a specific segment or portion on another entity (such as a line, path, or sequence).
-
D.
hasSuccessorSegment
Indicates that one segment directly follows another segment in a sequence or ordered structure.
-
E.
hasSegmentWith
Indicates that an entity contains or includes at least one segment that satisfies a specified condition or matches a given segment.
- 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_69f3493134b48190aa3c8cb523bd3800 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff5f5ecc808190b2df364da108ff4c |
completed | May 9, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ff5b84131c8190bf81d7fb53e934bc |
completed | May 9, 2026, 4:06 p.m. |
Created at: May 1, 2026, 1:09 a.m.