Triple
T6538691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laura (film) |
E168229
|
entity |
| Predicate | famousSongOrTheme |
P7259
|
FINISHED |
| Object | Laura (theme) |
—
|
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: Laura (theme) | Statement: [Laura (film), famousSongOrTheme, Laura (theme)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousSongOrTheme Context triple: [Laura (film), famousSongOrTheme, Laura (theme)]
-
A.
hasThemeSong
chosen
Indicates that an entity is associated with or characterized by a particular theme song.
-
B.
songMadeFamousBy
Indicates that a song became widely known or popular primarily through the performance, recording, or promotion of a particular artist or group.
-
C.
isPopularSongFrom
Indicates that a song is widely liked, well-known, or frequently played and originates from a particular source, such as an artist, album, or media work.
-
D.
singsAbout
Indicates that one entity performs a song whose subject or theme is another entity.
-
E.
isAnthemFor
Indicates that a song or musical composition serves as the official anthem representing a particular group, organization, place, or cause.
- 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_69c68a51564081909e93aee0dbd9cca3 |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6ce07332481909a5a7964282eb776 |
completed | March 27, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69c6acf3e3708190b052ec774e607cb7 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:49 p.m.