Triple
T24402866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ben Raleigh |
E615226
|
entity |
| Predicate | hadWorkRecordedBy |
P96247
|
FINISHED |
| Object | The Ronettes |
—
|
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: The Ronettes | Statement: [Ben Raleigh, hadWorkRecordedBy, The Ronettes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadWorkRecordedBy Context triple: [Ben Raleigh, hadWorkRecordedBy, The Ronettes]
-
A.
hasWorkRecordedBy
chosen
Indicates that a particular work (such as a composition or piece) has been captured or documented in an audio or video recording made by a specified recorder or performer.
-
B.
hasWorkRecordingsOn
Indicates that an entity has associated work recordings stored on or linked to another entity (such as a medium, platform, or system).
-
C.
hasWorkRecordedThere
Indicates that a person or creator has had their work documented, produced, or otherwise officially recorded at a particular place or institution.
-
D.
hasWorkedFor
Indicates that an entity has been employed by or has provided work or services to another entity.
-
E.
recordedInWork
Indicates that an action, event, or piece of information is documented or captured within a specific work (such as a book, article, or other created resource).
- 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_69e2d7e780bc81908049c779e697a7f6 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294dc1240819085aba9a8c2e07f42 |
completed | April 29, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:05 a.m.