Triple
T22919873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur – In the Minimoys Kingdom |
E568830
|
entity |
| Predicate | hasThemingStyle |
P62774
|
FINISHED |
| Object | fantasy |
—
|
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: fantasy | Statement: [Arthur – In the Minimoys Kingdom, hasThemingStyle, fantasy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThemingStyle Context triple: [Arthur – In the Minimoys Kingdom, hasThemingStyle, fantasy]
-
A.
hasThemingDetail
Indicates that something includes or is associated with a specific thematic element, motif, or stylistic detail.
-
B.
supportsThemingSystem
Indicates that an entity is compatible with and can operate using a theming system for customizable appearance or style.
-
C.
hasThemeType
chosen
Indicates that something is associated with or characterized by a particular thematic category or type.
-
D.
supportsThemingFormat
Indicates that an entity is compatible with and can correctly handle a particular theming format or style specification.
-
E.
usesThemeFrom
Indicates that one work incorporates, references, or is based on the thematic material of another work.
- 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_69e2458d90c88190a58cead4e781ca6a |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f180d40f98819096210c097b47d43b |
completed | April 29, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:42 p.m.