Triple
T1230447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foolish Fool |
E26425
|
entity |
| Predicate | hasReleaseFormat |
P5128
|
FINISHED |
| Object | vinyl single |
—
|
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: vinyl single | Statement: [Foolish Fool, hasReleaseFormat, vinyl single]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReleaseFormat Context triple: [Foolish Fool, hasReleaseFormat, vinyl single]
-
A.
hasRelease
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
-
B.
hasPublishingFormat
chosen
Indicates that an entity is associated with a specific format or medium in which it is published or made publicly available.
-
C.
hasReleaseModel
Indicates the type or strategy of release associated with an entity, such as how or under what model it is made available.
-
D.
firstReleaseFormat
Indicates the original medium or format in which something (such as a work or product) was first released.
-
E.
hasDigitalForm
Indicates that something exists or is available in a digital or electronic format.
- 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_69a4948571c88190a9191e451e6035fd |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be585674819099218b19ca9e7c66 |
completed | March 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69a4bb65d61c8190bf0424ea0019a98b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.