Triple
T1011580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Trolley Song |
E21834
|
entity |
| Predicate | hasChorusLyric |
P18290
|
FINISHED |
| Object | Clang, clang, clang went the trolley |
—
|
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: Clang, clang, clang went the trolley | Statement: [The Trolley Song, hasChorusLyric, Clang, clang, clang went the trolley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChorusLyric Context triple: [The Trolley Song, hasChorusLyric, Clang, clang, clang went the trolley]
-
A.
hasChorus
Indicates that something (typically a song or musical piece) includes a chorus section as part of its structure.
-
B.
hasChoir
Indicates that an entity possesses, maintains, or is associated with a choir.
-
C.
hasLyric
chosen
Indicates that one entity (typically a musical work or track) contains or is associated with the lyrics provided by another entity.
-
D.
hasChant
Indicates that an entity is associated with or characterized by a particular chant.
-
E.
hasVariableLyrics
Indicates that the lyrics of a song or musical piece change between different performances, versions, or contexts.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7be907c8190b5c6ea89257755a7 |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b72207c08190a3dbb2aa7acbbc71 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.