Triple
T26563966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scott C3a (block format) |
E666325
|
entity |
| Predicate | hasGum |
P161725
|
FINISHED |
| Object | original gum (for mint examples) |
—
|
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: original gum (for mint examples) | Statement: [Scott C3a (block format), hasGum, original gum (for mint examples)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGum Context triple: [Scott C3a (block format), hasGum, original gum (for mint examples)]
-
A.
isChewingGum
Indicates that an entity is performing the action of chewing gum.
-
B.
hasTeeth
Indicates that one entity possesses teeth as a physical feature.
-
C.
hasGadget
Indicates that an entity possesses, uses, or is equipped with a particular gadget.
-
D.
hasJaw
Indicates that one entity possesses or is equipped with a jaw as a physical anatomical feature.
-
E.
toothUsedBy
Indicates that a tooth is utilized or employed by a particular entity (such as an organism or tool) for some function or action.
- 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_69ee9cf7e94481909f0d556b36e43572 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6200ac60481909895c61d050b1338 |
completed | May 2, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61f109ef48190873bfe18638d2046 |
completed | May 2, 2026, 3:58 p.m. |
Created at: April 27, 2026, 1:54 a.m.