Triple
T31314481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Manuscript |
E798553
|
entity |
| Predicate | hasExclusiveTracks |
P69779
|
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: [The Manuscript, hasExclusiveTracks, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExclusiveTracks Context triple: [The Manuscript, hasExclusiveTracks, yes]
-
A.
containsAdditionalTracksBeyond
chosen
Indicates that one entity includes more tracks or items than are present in another referenced set or version.
-
B.
hasBonusTrackStatus
Indicates whether an item (such as a track or release) is designated as a bonus track in relation to a primary work or edition.
-
C.
hasDeluxeEditionTrackCount
Indicates the number of tracks included in the deluxe edition of a given release or work.
-
D.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
E.
hasExclusiveContractFor
Indicates that one party holds sole contractual rights to provide, use, or represent a specific product, service, or opportunity, excluding all other potential counterparties.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 29, 2026, 9:15 p.m.