Triple
T19978973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Wonders of the East |
E493764
|
entity |
| Predicate | describesMotif |
P41002
|
FINISHED |
| Object | monstrous races |
—
|
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: monstrous races | Statement: [The Wonders of the East, describesMotif, monstrous races]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesMotif Context triple: [The Wonders of the East, describesMotif, monstrous races]
-
A.
featuresMotif
chosen
Indicates that something contains, incorporates, or prominently includes a particular recurring motif or pattern.
-
B.
openingMotifDescription
Indicates a description of the initial recurring musical or thematic idea that begins a work or section.
-
C.
transformationMotif
Indicates a recurring pattern or theme in which one entity undergoes a change in form, state, or identity in relation to another.
-
D.
usesMotifsFrom
Indicates that one entity incorporates or draws upon recurring themes, patterns, or elements that originate from another entity.
-
E.
primaryMotif
Indicates that one entity serves as the main recurring theme or dominant motif associated with another entity.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d11108481908241a2a96a795a7d |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:27 p.m.