Triple
T33550564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | To Turn the Stone |
E859319
|
entity |
| Predicate | recordedByMemberOf |
P102130
|
FINISHED |
| Object | ABBA |
—
|
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: ABBA | Statement: [To Turn the Stone, recordedByMemberOf, ABBA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordedByMemberOf Context triple: [To Turn the Stone, recordedByMemberOf, ABBA]
-
A.
recordedByFormerMemberOf
Indicates that something (typically a work or performance) was recorded by an individual who was previously, but is no longer, a member of a specified group or organization.
-
B.
recordedByBandMemberOf
Indicates that a recording was made by an individual who is a member of a specified band.
-
C.
recordedByCollective
chosen
Indicates that an event, action, or piece of data was recorded by a group or collective entity rather than by an individual.
-
D.
membershipRecordedBy
Indicates that the recording or documentation of a membership was carried out or created by a specific agent or system.
-
E.
bandMemberOnRecording
Indicates that a person is a member of a band who performed on a specific recording.
- 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_69f3497b2b68819093207971b5e13dc8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 1, 2026, 1:39 a.m.