Triple
T11124477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elite Hotel |
E263098
|
entity |
| Predicate | reissuedOnFormat |
P97671
|
FINISHED |
| Object | compact disc |
—
|
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: compact disc | Statement: [Elite Hotel, reissuedOnFormat, compact disc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reissuedOnFormat Context triple: [Elite Hotel, reissuedOnFormat, compact disc]
-
A.
reReleaseDate
Indicates the date on which something is released again, such as a reissued or updated version of an existing item.
-
B.
wasReissued
Indicates that an item, such as a document or edition, has been issued again after its original release.
-
C.
reissueIncludes
Indicates that a reissued version of something contains or incorporates the referenced item as part of that reissue.
-
D.
revisedEditionDate
Indicates the date on which a work was issued or published as a revised edition.
-
E.
reissueFeature
Indicates that an existing item (such as a product, document, or media release) is being issued again, typically with updates, changes, or in a new edition or format.
- F. None of above. chosen
Provenance (4 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7e82e933481908550499cf9dd6531 |
completed | April 9, 2026, 5:55 p.m. |
| PD | Predicate disambiguation | batch_69d7441efe948190ae4ab020121e169d |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d75112eb1c8190ba1dd51e42e8a7e8 |
completed | April 9, 2026, 7:11 a.m. |
Created at: April 8, 2026, 9:28 p.m.