Triple
T17908389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bloooo |
E447759
|
entity |
| Predicate | featuresImaginaryFriends |
P115956
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Bloooo, featuresImaginaryFriends, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresImaginaryFriends Context triple: [Bloooo, featuresImaginaryFriends, yes]
-
A.
hasImaginaryFriendCharacter
Indicates that an entity is associated with or has an imaginary friend character.
-
B.
featuresFictionalElement
chosen
Indicates that one entity includes, presents, or incorporates a fictional element (such as an imaginary character, place, object, or concept) as part of its content or composition.
-
C.
featuresFictionalProgram
Indicates that a work includes or presents a fictional program (such as a TV show, software, or in-universe broadcast) as part of its content.
-
D.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
E.
featuresAlien
Indicates that something includes, presents, or prominently involves an alien or extraterrestrial being.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49e9e4c9881908bfc3a83809d6b85 |
completed | April 19, 2026, 9:21 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:19 a.m.