Triple
T32434527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gibson ES-335 |
E828819
|
entity |
| Predicate | isThinline |
P174082
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Gibson ES-335, isThinline, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isThinline Context triple: [Gibson ES-335, isThinline, yes]
-
A.
isSmall
Indicates that one entity has a size that is relatively small, either in absolute terms or compared to a reference standard or another entity.
-
B.
isTight
Indicates that one entity fits closely or securely around, against, or within another without looseness or extra space.
-
C.
isNarrow
Indicates that something has a small width or limited breadth relative to a reference or context.
-
D.
isShort
Indicates that one entity has a relatively small height, length, or duration compared to a standard or to other entities.
-
E.
isShortLine
Indicates that a line is relatively short in length compared to a standard or other lines.
- 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_69f3491bf298819097b610f772d54a6d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2b0d31c8190adb202fdf21d4797 |
completed | May 3, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bb344bb48190a8089f29c0063ded |
completed | May 3, 2026, 3:04 a.m. |
Created at: May 1, 2026, 12:55 a.m.