Triple
T6378408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucille (B.B. King’s guitar) |
E143521
|
entity |
| Predicate | hasInlay |
P38145
|
FINISHED |
| Object | block inlays |
—
|
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: block inlays | Statement: [Lucille (B.B. King’s guitar), hasInlay, block inlays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInlay Context triple: [Lucille (B.B. King’s guitar), hasInlay, block inlays]
-
A.
hasInfield
Indicates that an entity possesses or includes a designated infield area, typically within a larger spatial or structural context.
-
B.
hasInlet
Indicates that one entity serves as an inlet or entry point through which another entity receives a flow of material, energy, or fluid.
-
C.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
D.
hasDecor
chosen
Indicates that one entity possesses, features, or is adorned with a particular decorative element or style.
-
E.
hasCodeIn
Indicates that one entity is represented, defined, or implemented within the codebase or coding context of another entity.
- 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_69c008d9f4348190ab598a2913259a1c |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0683ed0788190b00f626c76a71ea2 |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060eff524819094cee1c70a0c1ff4 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:33 p.m.