Triple
T33268936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grizzly moist snuff |
E851725
|
entity |
| Predicate | hasCutType |
P84047
|
FINISHED |
| Object | long cut |
—
|
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: long cut | Statement: [Grizzly moist snuff, hasCutType, long cut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCutType Context triple: [Grizzly moist snuff, hasCutType, long cut]
-
A.
hasCut
Indicates that one entity has made or possesses a cut in, on, or through another entity.
-
B.
hasTypicalCut
chosen
Indicates that one entity is characterized by or associated with a standard or typical type of cut of another entity.
-
C.
isCutInto
Indicates that one entity is divided or separated into pieces or segments that become the other entity.
-
D.
hasAlternateCut
Indicates that an entity has an alternative edited version or cut, distinct from its primary or original form.
-
E.
hasSlitType
Indicates that an entity possesses or is characterized by a specific type or form of slit.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: May 1, 2026, 1:32 a.m.