Triple
T38114124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jibbitz charms |
E951744
|
entity |
| Predicate | attachmentMechanism |
P42077
|
FINISHED |
| Object | snap-in plug |
—
|
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: snap-in plug | Statement: [Jibbitz charms, attachmentMechanism, snap-in plug]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attachmentMechanism Context triple: [Jibbitz charms, attachmentMechanism, snap-in plug]
-
A.
attachmentMethod
chosen
Indicates the way or technique by which one entity is fastened, joined, or secured to another.
-
B.
attachmentType
Indicates the specific kind or category of attachment that relates one entity to another.
-
C.
extensionMechanism
Indicates that one entity provides a way to extend, customize, or add new functionality or components to another entity.
-
D.
attachedTo
Indicates that one entity is physically or logically fastened, connected, or joined to another entity.
-
E.
mechanismBy
Indicates that one entity occurs, is produced, or is brought about by means of another entity, which serves as its mechanism or causal process.
- 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_69f76f07734c8190814e937e12257a78 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: May 3, 2026, 4:21 p.m.