Triple
T35187599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hobbes |
E1016030
|
entity |
| Predicate | visualFormForCalvin |
P11599
|
FINISHED |
| Object | living 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: living tiger | Statement: [Hobbes, visualFormForCalvin, living tiger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visualFormForCalvin Context triple: [Hobbes, visualFormForCalvin, living tiger]
-
A.
visualForm
chosen
Indicates the visual appearance, shape, or structural pattern that characterizes how something looks.
-
B.
envisionedForm
Indicates that one entity is the mental image, design, or conceptual form that another entity has imagined or planned.
-
C.
visualElements
Indicates that one entity contains, uses, or is characterized by specific visual components or graphical features associated with another entity.
-
D.
viewOnForms
Indicates that one entity has a particular perspective, opinion, or stance regarding forms, form-related processes, or form usage.
-
E.
inspiredByForm
Indicates that something’s design, structure, or style is influenced or shaped by the form or configuration of another thing.
- 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78dc3776c8190bbd4702acd5a191e |
completed | May 3, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.