Triple
T35187600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hobbes |
E1016030
|
entity |
| Predicate | visualFormForOthers |
P182592
|
FINISHED |
| Object | stuffed toy tiger |
—
|
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: stuffed toy tiger | Statement: [Hobbes, visualFormForOthers, stuffed toy tiger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visualFormForOthers Context triple: [Hobbes, visualFormForOthers, stuffed toy tiger]
-
A.
visualForm
Indicates the visual appearance, shape, or structural pattern that characterizes how something looks.
-
B.
alternativeForm
Indicates that one entity is an alternative version, variant, or representation of another entity.
-
C.
viewOnForms
Indicates that one entity has a particular perspective, opinion, or stance regarding forms, form-related processes, or form usage.
-
D.
envisionedForm
Indicates that one entity is the mental image, design, or conceptual form that another entity has imagined or planned.
-
E.
individualForm
Indicates that an entity is a specific, individual instance or form of something, distinguishing it from other forms or collective representations.
- 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7904a770481908ef3f788e51e8dba |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78f629d508190b755848162c4e101 |
completed | May 3, 2026, 6:09 p.m. |
Created at: May 3, 2026, 4:02 p.m.