Triple
T37339883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honey, We Shrunk Ourselves |
E927001
|
entity |
| Predicate | hasMiniaturizedCharacters |
P111069
|
FINISHED |
| Object | adults |
—
|
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: adults | Statement: [Honey, We Shrunk Ourselves, hasMiniaturizedCharacters, adults]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMiniaturizedCharacters Context triple: [Honey, We Shrunk Ourselves, hasMiniaturizedCharacters, adults]
-
A.
hasMiniature
Indicates that one entity possesses or includes a smaller-scale representation or model of another entity.
-
B.
hasApproximateNumberOfMiniatures
Indicates that an entity is associated with an estimated or non-exact count of miniatures.
-
C.
hasFullSizedCharacters
Indicates that the subject includes characters rendered at full, standard size rather than reduced or miniature forms.
-
D.
hasCharacters
chosen
Indicates that an entity (such as a work or story) includes or features certain characters as part of its content.
-
E.
hasIconicCharacter
Indicates that something is associated with a character widely recognized as emblematic or highly representative of it.
- 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_69f76eb4e8a881908bd40da28f36fc7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 3, 2026, 4:16 p.m.