Triple
T28682305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kleenex |
E726038
|
entity |
| Predicate | hasGenericUse |
P180230
|
FINISHED |
| Object | facial tissue |
—
|
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: facial tissue | Statement: [Kleenex, hasGenericUse, facial tissue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenericUse Context triple: [Kleenex, hasGenericUse, facial tissue]
-
A.
hasGeneralPurpose
Indicates that one entity serves as the broad, overarching function, role, or intended use of another entity.
-
B.
isGenericAvailable
Indicates that a non-brand (generic) version of a product, typically a medication, is available as an alternative.
-
C.
isGenericUseBeyondCountry
Indicates that something is used in a general or non-specific way outside the boundaries of a particular country.
-
D.
isGeneralPurposeIn
Indicates that something serves a broad, non-specialized function or use within a specified context, domain, or environment.
-
E.
usedAsGeneral
Indicates that an entity served in the role or capacity of a general, typically as a high-ranking military commander.
- 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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
| PDg | Predicate description generation | batch_69f739a58b3c81908abc2b8738a65678 |
completed | May 3, 2026, 12:03 p.m. |
Created at: April 28, 2026, 5:10 a.m.