Triple
T32434554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gibson ES-335 |
E828819
|
entity |
| Predicate | typicalFinishOptions |
P193689
|
FINISHED |
| Object | cherry |
—
|
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: cherry | Statement: [Gibson ES-335, typicalFinishOptions, cherry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFinishOptions Context triple: [Gibson ES-335, typicalFinishOptions, cherry]
-
A.
typicalFinish
Indicates that an action, process, or event commonly or characteristically ends with a particular outcome or state.
-
B.
decorativeFinish
Indicates that one entity serves as an ornamental or aesthetic surface treatment applied to another entity.
-
C.
hasTypicalFinish
Indicates that one entity characteristically or commonly concludes, completes, or ends with another entity.
-
D.
standardFinish
chosen
Indicates that an entity has a typical or commonly accepted type of finish, coating, or surface treatment applied to it.
-
E.
finishingMethod
Indicates the technique or process used to complete or finalize an object, task, or work.
- 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_69f3491bf298819097b610f772d54a6d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:55 a.m.