Triple
T8771012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Fleece |
E208459
|
entity |
| Predicate | associatedMotif |
P41002
|
FINISHED |
| Object | dragon-guarded treasure |
—
|
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: dragon-guarded treasure | Statement: [Golden Fleece, associatedMotif, dragon-guarded treasure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedMotif Context triple: [Golden Fleece, associatedMotif, dragon-guarded treasure]
-
A.
usesMotifsFrom
Indicates that one entity incorporates or draws upon recurring themes, patterns, or elements that originate from another entity.
-
B.
featuresMotif
chosen
Indicates that something contains, incorporates, or prominently includes a particular recurring motif or pattern.
-
C.
sharesMotifsWith
Indicates that two entities contain or employ similar recurring themes, patterns, or symbolic elements.
-
D.
primaryMotif
Indicates that one entity serves as the main recurring theme or dominant motif associated with another entity.
-
E.
mutationAssociatedWith
Indicates that a specific genetic mutation is linked or related to another entity, such as a disease, trait, or molecular effect.
- 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_69ca835edb4481909b4aafb616dc5eb7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f2b08f881909f3d4fab2eda1d67 |
completed | March 31, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1aff3881908be6a9cbc9f50461 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:41 p.m.