Triple
T30361164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Promise box set |
E772289
|
entity |
| Predicate | containsFormat |
P198651
|
FINISHED |
| Object | CD |
—
|
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: CD | Statement: [The Promise box set, containsFormat, CD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsFormat Context triple: [The Promise box set, containsFormat, CD]
-
A.
hasMatchFormat
Indicates that something (such as a game, event, or competition) is conducted according to a specified match format or structure.
-
B.
hasFormatElement
Indicates that one entity includes, is composed of, or is associated with a specific structural or formatting component of its overall format.
-
C.
hasFormatCurrent
Indicates that an entity is available or expressed in the currently used or most up-to-date format.
-
D.
hasFileFormat
Indicates that one entity (typically a digital file or resource) is encoded, stored, or represented using a specific file format defined by the other entity.
-
E.
includeFormat
Indicates that one entity contains or specifies the format or representation type of another entity.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fefa064ab48190925759950d0d94d9 |
completed | May 9, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69fef96ae5d08190b027435753c44821 |
completed | May 9, 2026, 9:07 a.m. |
| PDg | Predicate description generation | batch_69fefa05757481908fa38f5c604afbbe |
completed | May 9, 2026, 9:10 a.m. |
Created at: April 29, 2026, 7:58 p.m.