Triple
T23425035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guild S-100 |
E560770
|
entity |
| Predicate | headstockLogo |
P97633
|
FINISHED |
| Object | Guild logo |
—
|
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: Guild logo | Statement: [Guild S-100, headstockLogo, Guild logo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headstockLogo Context triple: [Guild S-100, headstockLogo, Guild logo]
-
A.
headstockType
Indicates the specific style or configuration of a headstock used in relation to another object or entity.
-
B.
headstockShape
Indicates the specific contour or outline form of an object’s headstock relative to other parts or designs.
-
C.
headstockInlay
chosen
Indicates that one entity is an inlay decoration located on the headstock of another entity (typically a stringed instrument).
-
D.
headStatus
Indicates the current condition, role, or state of an entity in its capacity as a head or leader within a given context.
-
E.
headType
Indicates the specific kind or category of head associated with an entity (e.g., type of head part, head role, or head classification in a structure or system).
- 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a54951688190a3c5382971af3e41 |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:47 p.m.