Triple
T2190380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Band-Aid |
E49846
|
entity |
| Predicate | genericUseMeaning |
P2529
|
FINISHED |
| Object | any small adhesive bandage |
—
|
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: any small adhesive bandage | Statement: [Band-Aid, genericUseMeaning, any small adhesive bandage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genericUseMeaning Context triple: [Band-Aid, genericUseMeaning, any small adhesive bandage]
-
A.
commonMeaning
Indicates that multiple entities share the same or very similar meaning or semantic interpretation.
-
B.
reasonForUse
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
-
C.
usageType
chosen
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
-
D.
possibleMeaning
Indicates that something may plausibly represent, signify, or be interpreted as a particular meaning or sense.
-
E.
eligibleUses
Indicates the types of actions, purposes, or contexts in which something is permitted or qualified to be used.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf9e99f08190892d34485c8f2f25 |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda32d1881909d1fd83a751fb21c |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.