Triple
T24708003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destroyer |
E611948
|
entity |
| Predicate | notableBallad |
P166560
|
FINISHED |
| Object | Beth |
—
|
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: Beth | Statement: [Destroyer, notableBallad, Beth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBallad Context triple: [Destroyer, notableBallad, Beth]
-
A.
notableTune
Indicates that a tune is especially significant, well-known, or characteristic in relation to a particular entity.
-
B.
notableSongbook
Indicates that there is a notable or significant songbook associated with the given entity.
-
C.
notableSongWrittenFor
Indicates that a particular song was specifically written for a given person, group, work, event, or purpose.
-
D.
notableTrack
Indicates that a particular track (such as a song or recording) is especially significant, well-known, or prominent in relation to the subject.
-
E.
notableChorus
Indicates that an entity is recognized for having a particularly prominent or distinguished chorus section.
- F. None of above. chosen
Provenance (4 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_69e2c4d9c24c8190a3712d74327f0c6e |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f662a29b3881909957a7e3b986653c |
completed | May 2, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 18, 2026, 3:24 a.m.