Triple
T23680614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giasone |
E585006
|
entity |
| Predicate | hasModernRecordings |
P131543
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Giasone, hasModernRecordings, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernRecordings Context triple: [Giasone, hasModernRecordings, true]
-
A.
hasStudioRecordings
chosen
Indicates that one entity possesses or is associated with studio-made audio recordings of another entity.
-
B.
hasModernPerformances
Indicates that the subject work or piece is currently being performed or staged in modern times.
-
C.
hasRecordingLegacy
Indicates that an entity is associated with a historical or prior version of a recording, capturing its legacy or earlier state.
-
D.
isRecordedMusicFor
Indicates that one entity is music that has been recorded specifically to accompany, represent, or be used with another entity (such as a work, event, or medium).
-
E.
hasRecordingHistory
Indicates that an entity has an associated record of past recordings or recorded events.
- 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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f835ec8190a7bdcfa48ad79cd5 |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:51 p.m.