Triple
T5514607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sorta Seafoam |
E144649
|
entity |
| Predicate | finishType |
P65191
|
FINISHED |
| Object | two-tone back finish |
—
|
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: two-tone back finish | Statement: [Sorta Seafoam, finishType, two-tone back finish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finishType Context triple: [Sorta Seafoam, finishType, two-tone back finish]
-
A.
finishOptions
Indicates that one entity specifies or controls the possible ways in which another entity can be completed, finalized, or brought to an end.
-
B.
finished
Indicates that an entity has completed an action, process, or state, reaching its end point.
-
C.
startFinishType
Indicates the specific way in which an activity, event, or process begins and/or ends (e.g., its initiation and completion characteristics).
-
D.
finalStep
Indicates that an action or state represents the last step or concluding stage in a process or sequence.
-
E.
finishPosition
Indicates the final rank or place an entity achieves in an ordered outcome, such as a race, competition, or sequence of results.
- 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_69c008f77ff88190b0cd50ca207295d1 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f5b4e988190b590b4157cf089c1 |
completed | March 22, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69c01b0a06348190b39ac9fe80d2836a |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f051e508190b3886d87b4afdd0b |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:33 p.m.