Triple
T29721717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M. 55 |
E752070
|
entity |
| Predicate | usedInRecordingsMetadata |
P192144
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [M. 55, usedInRecordingsMetadata, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInRecordingsMetadata Context triple: [M. 55, usedInRecordingsMetadata, yes]
-
A.
usedForRecordingBy
Indicates that something serves as a medium, tool, or device that is employed by an agent to make a recording.
-
B.
reRecordedWith
Indicates that an existing recording was made again in collaboration with the specified entity (such as an artist, group, or producer).
-
C.
reRecordedIn
Indicates that an existing recording of something (e.g., a performance or audio/video content) was made again and captured in a new recording instance.
-
D.
includesRecordingsBy
Indicates that one entity (such as a collection, album, or compilation) contains or features recordings created or performed by another entity (such as an artist or group).
-
E.
recordedFor
Indicates that something has been documented, captured, or logged on behalf of or in association with a particular entity or context.
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
| PDg | Predicate description generation | batch_69fcf82405c88190a19cecf8e9cc272d |
completed | May 7, 2026, 8:37 p.m. |
Created at: April 28, 2026, 7:36 p.m.