Triple
T26195262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frankenstrat guitar |
E655078
|
entity |
| Predicate | finishPattern |
P160031
|
FINISHED |
| Object | black and white stripes |
—
|
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: black and white stripes | Statement: [Frankenstrat guitar, finishPattern, black and white stripes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finishPattern Context triple: [Frankenstrat guitar, finishPattern, black and white stripes]
-
A.
finishType
Indicates the manner or outcome by which an action, process, or event is completed.
-
B.
finishSetting
Indicates that an entity completes configuring or establishing a particular setting or set of settings for another entity or context.
-
C.
finishOptions
Indicates that one entity specifies or controls the possible ways in which another entity can be completed, finalized, or brought to an end.
-
D.
finishDescription
Indicates that an entity completes or provides the remaining details or explanation about another entity or item.
-
E.
finish
Indicates that an entity brings an action, process, or state to an end or completion.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60ca5cd78819083f0216b359da470 |
completed | May 2, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 8:46 p.m.