Triple
T32398443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Wrecked |
E827874
|
entity |
| Predicate | hasRockStarCharacter |
P62476
|
FINISHED |
| Object | Jason Masters |
—
|
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: Jason Masters | Statement: [Love Wrecked, hasRockStarCharacter, Jason Masters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRockStarCharacter Context triple: [Love Wrecked, hasRockStarCharacter, Jason Masters]
-
A.
hasRock
Indicates that one entity possesses, contains, or is associated with a rock.
-
B.
hasFictionalPerformer
chosen
Indicates that an entity is associated with a performer who is a fictional or imaginary character rather than a real person.
-
C.
hasFrontmanRole
Indicates that an entity holds the primary lead or frontman role within a group, band, or ensemble.
-
D.
hasRockRecord
Indicates that an entity possesses or is associated with a documented record related to rock music or rock materials.
-
E.
hasRockRecordIn
Indicates that an entity has a recorded instance or documentation of rock-related data, activity, or presence within a specified context or location.
- 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: May 1, 2026, 12:52 a.m.