Triple
T12840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Love You, California |
E258
|
entity |
| Predicate | musicForm |
P130
|
FINISHED |
| Object | song with chorus and verses |
—
|
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 with chorus and verses | Statement: [I Love You, California, musicForm, song with chorus and verses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicForm Context triple: [I Love You, California, musicForm, song with chorus and verses]
-
A.
musicTradition
Indicates a relationship where one entity follows, embodies, or belongs to a particular musical tradition or style associated with another entity.
-
B.
format
chosen
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
C.
genre
Indicates the artistic or thematic category to which a work (such as a book, film, or song) belongs.
-
D.
signedInstrument
Indicates that an entity has formally signed or executed a specific document, contract, or other legal instrument.
-
E.
stateSong
Indicates that a particular song is officially designated as the state song of a given state or region.
- 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_69a23d7ad88c8190bffe8ab091d86642 |
completed | Feb. 28, 2026, 12:57 a.m. |
| NER | Named-entity recognition | batch_69a243abb2ec8190937365e5ecec52ad |
completed | Feb. 28, 2026, 1:23 a.m. |
| PD | Predicate disambiguation | batch_69a23fe9470c8190918a6ca1df168646 |
completed | Feb. 28, 2026, 1:07 a.m. |
Created at: Feb. 28, 2026, 1:02 a.m.