Triple
T4663532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avengers Grimm |
E102789
|
entity |
| Predicate | blendsElement |
P47548
|
FINISHED |
| Object | fairy-tale characters |
—
|
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: fairy-tale characters | Statement: [Avengers Grimm, blendsElement, fairy-tale characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blendsElement Context triple: [Avengers Grimm, blendsElement, fairy-tale characters]
-
A.
mixesElementsOf
chosen
Indicates a relationship where one entity combines or blends components, features, or aspects of another entity or set of entities into a unified whole.
-
B.
usedInBlends
Indicates that something serves as an ingredient or component within one or more mixtures, combinations, or blends.
-
C.
typicalBlendStyle
Indicates the usual or characteristic way in which two or more elements are combined or mixed together.
-
D.
mixesWith
Indicates that one entity is combined or blended together with another entity to form a mixture.
-
E.
usesElement
Indicates that one entity makes use of, incorporates, or depends on a specified element in its structure, function, or behavior.
- 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_69bd43d9cba4819086c1ab1c2d9d2133 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd632d6150819085bab97021c0235a |
completed | March 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69bd62126b0c81909ba3f21b21e30d54 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.