Triple
T29221010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaos in Motion Tour |
E740803
|
entity |
| Predicate | associatedReleaseType |
P111480
|
FINISHED |
| Object | live album |
—
|
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: live album | Statement: [Chaos in Motion Tour, associatedReleaseType, live album]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedReleaseType Context triple: [Chaos in Motion Tour, associatedReleaseType, live album]
-
A.
associatedWithRelease
chosen
Indicates a relationship where something is linked or connected to a particular release event, version, or distribution.
-
B.
alsoReleases
Indicates that the subject entity issues or publishes additional releases beyond a primary or previously mentioned release.
-
C.
alsoReleased
Indicates that two or more items were released at the same time or as part of the same release event.
-
D.
alsoReleasesIn
Indicates that the same work, product, or content is released in an additional region, format, or context beyond its primary release.
-
E.
associatedActType
Indicates that one action or event is linked or related to another specific type of action or event.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a0337c7389c8190b71d27b8eb8daf9a |
completed | May 12, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_6a0335b7b1588190b02a0ce6a08704aa |
completed | May 12, 2026, 2:14 p.m. |
Created at: April 28, 2026, 12:15 p.m.