Triple
T37464488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twinspell |
E930999
|
entity |
| Predicate | belongsToFormatAtRelease |
P59045
|
FINISHED |
| Object | Standard |
—
|
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: Standard | Statement: [Twinspell, belongsToFormatAtRelease, Standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToFormatAtRelease Context triple: [Twinspell, belongsToFormatAtRelease, Standard]
-
A.
isAReleaseOf
Indicates that one entity is a specific release, edition, or version of another entity.
-
B.
subsequentReleaseFormat
Indicates that one media release is issued in a different format that chronologically follows an earlier release of the same content.
-
C.
workAppearedInReleaseFormat
Indicates that a particular work was included in, or made available through, a specific release format (such as a medium, edition, or distribution type).
-
D.
containsFormat
Indicates that one entity includes or is associated with a particular format type as part of its content or representation.
-
E.
formatReleased
chosen
Indicates that a particular release or version of something is made available in a specified format (such as digital, physical, or a specific file type).
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a002249ee388190a9501ee7630dc658 |
completed | May 10, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_6a002189273881909b6b687e2d61f5b1 |
completed | May 10, 2026, 6:11 a.m. |
Created at: May 3, 2026, 4:17 p.m.