Triple
T21872755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siberian Khatru |
E540048
|
entity |
| Predicate | openingTrackOfSide |
P55756
|
FINISHED |
| Object | Close to the Edge side two |
—
|
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: Close to the Edge side two | Statement: [Siberian Khatru, openingTrackOfSide, Close to the Edge side two]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingTrackOfSide Context triple: [Siberian Khatru, openingTrackOfSide, Close to the Edge side two]
-
A.
sideTwoOpeningTrack
chosen
Indicates that the related item is the first (opening) track on the second side of a multi-sided audio recording or release.
-
B.
openingTrackOfFilm
Indicates that a musical track serves as the first or introductory piece in the soundtrack of a specified film.
-
C.
usedAsOpeningTrackOf
Indicates that a musical work serves as the first (opening) track on a specified release or recording.
-
D.
side1Track
Indicates that an entity is associated with or belongs to the first side or track in a two-sided or multi-track configuration.
-
E.
openingRace
Indicates that one race serves as the initial or first event in a sequence of races or a racing competition.
- 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0f337ab5c8190937a457d348c732b |
completed | April 28, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7 p.m.