Triple
T26894984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andreas Deja |
E677874
|
entity |
| Predicate | blogFocus |
P109058
|
FINISHED |
| Object | classic Disney animation history |
—
|
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: classic Disney animation history | Statement: [Andreas Deja, blogFocus, classic Disney animation history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blogFocus Context triple: [Andreas Deja, blogFocus, classic Disney animation history]
-
A.
categoryFocus
Indicates that one entity is the primary subject, theme, or focal point within the broader category defined by the other entity.
-
B.
writingFocus
Indicates that an entity’s primary attention or effort is directed toward writing or written expression.
-
C.
brandFocus
Indicates that a brand primarily concentrates its efforts, messaging, or resources on a particular target, theme, or market segment.
-
D.
creativeWorkFocus
chosen
Indicates that one entity is the primary subject, theme, or focal point of another entity’s creative work.
-
E.
commentaryFocus
Indicates that an item of commentary is primarily directed toward or centered on a particular entity, topic, or aspect.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61fa9a1ec8190bc4063656815a1c5 |
completed | May 2, 2026, 4 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:47 a.m.