Triple
T35187629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Susie Derkins |
E1016031
|
entity |
| Predicate | hasImaginaryPlay |
P185694
|
FINISHED |
| Object | playing house with Calvin |
—
|
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: playing house with Calvin | Statement: [Susie Derkins, hasImaginaryPlay, playing house with Calvin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImaginaryPlay Context triple: [Susie Derkins, hasImaginaryPlay, playing house with Calvin]
-
A.
hasImaginaryCharacter
Indicates that an entity includes, features, or is associated with a fictional or imaginary character.
-
B.
isImaginary
Indicates that something exists only in the mind or imagination and does not have a corresponding real-world or physical existence.
-
C.
hasImaginaryElement
Indicates that an entity includes or is associated with an imaginary (non-real) component, typically in a mathematical or conceptual sense.
-
D.
hasImaginaryFriendCharacter
Indicates that an entity is associated with or has an imaginary friend character.
-
E.
hasImaginaryControlOver
Indicates a perceived or illusory ability of one entity to direct, influence, or command another, without any actual control existing in reality.
- 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_69f7c33d59808190b647989a093f3488 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c29cf36481908e472d4dcb5573b9 |
completed | May 3, 2026, 9:48 p.m. |
Created at: May 3, 2026, 4:02 p.m.