Triple
T8592576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dala horse |
E203463
|
entity |
| Predicate | hasTypicalMotifOrigin |
P31989
|
FINISHED |
| Object | biblical kurbits painting tradition |
—
|
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: biblical kurbits painting tradition | Statement: [Dala horse, hasTypicalMotifOrigin, biblical kurbits painting tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalMotifOrigin Context triple: [Dala horse, hasTypicalMotifOrigin, biblical kurbits painting tradition]
-
A.
usesMotifsFrom
chosen
Indicates that one entity incorporates or draws upon recurring themes, patterns, or elements that originate from another entity.
-
B.
featuresMotif
Indicates that something contains, incorporates, or prominently includes a particular recurring motif or pattern.
-
C.
primaryMotif
Indicates that one entity serves as the main recurring theme or dominant motif associated with another entity.
-
D.
hasRhythmicOrigin
Indicates that something originates from, is derived from, or is fundamentally based on rhythm or rhythmic patterns.
-
E.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
- 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_69ca832a7f108190b4e4f5648abf4aa2 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46c5e8888190b721e791c449b0df |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454504448190aaad2af8b17357cd |
completed | March 31, 2026, 10:05 p.m. |
Created at: March 30, 2026, 6:23 p.m.