Triple
T33293874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Live! |
E852386
|
entity |
| Predicate | hasRecordingMode |
P110820
|
FINISHED |
| Object | analog |
—
|
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: analog | Statement: [Live!, hasRecordingMode, analog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecordingMode Context triple: [Live!, hasRecordingMode, analog]
-
A.
recordingMode
chosen
Indicates the method or configuration by which something is recorded, such as how data, audio, or video capture is performed.
-
B.
hasRecordingContract
Indicates that an entity is formally bound by an agreement to produce recordings for another entity, typically a record label or similar organization.
-
C.
hasVideoRecordingAvailableOn
Indicates that a video recording of something is accessible or hosted on a specified platform, service, or medium.
-
D.
hasRecordingLegacy
Indicates that an entity is associated with a historical or prior version of a recording, capturing its legacy or earlier state.
-
E.
isOnSoundRecording
Indicates that a work, performance, or content is fixed or contained on a particular sound 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a036f0569cc8190a8ac7f4e07145d15 |
completed | May 12, 2026, 6:18 p.m. |
| PD | Predicate disambiguation | batch_6a036c42cf2481908760c7d48b9fc001 |
completed | May 12, 2026, 6:06 p.m. |
Created at: May 1, 2026, 1:33 a.m.