Triple
T28354208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SFP9 |
E718179
|
entity |
| Predicate | magazineReleaseType |
P128256
|
FINISHED |
| Object | paddle-style magazine release (common configuration) |
—
|
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: paddle-style magazine release (common configuration) | Statement: [SFP9, magazineReleaseType, paddle-style magazine release (common configuration)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: magazineReleaseType Context triple: [SFP9, magazineReleaseType, paddle-style magazine release (common configuration)]
-
A.
magazineRelease
Indicates the event or relationship in which a magazine is issued or made publicly available on a particular date or through a specific channel.
-
B.
magazineType
Indicates the specific category or genre to which a magazine belongs.
-
C.
magazineIssueNumber
Indicates the specific issue number assigned to a magazine within its publication sequence.
-
D.
ownedMagazine
Indicates that one entity possessed or held ownership of a particular magazine.
-
E.
typicalMagazineType
chosen
Indicates that one entity is the magazine type that is most commonly or characteristically associated with the other entity.
- 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_69eff6ec27b481908c8d7b86c47893d9 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64c2ad8648190a840aeb28c5bfd40 |
completed | May 2, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 12:48 a.m.