Triple
T25251235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turul monument |
E632745
|
entity |
| Predicate | usesMotive |
P140132
|
FINISHED |
| Object | Turul in Hungarian mythology |
—
|
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: Turul in Hungarian mythology | Statement: [Turul monument, usesMotive, Turul in Hungarian mythology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMotive Context triple: [Turul monument, usesMotive, Turul in Hungarian mythology]
-
A.
motive
Indicates the underlying reason, intention, or driving force that explains why an entity performs or is associated with a particular action or event.
-
B.
hasMotiveTheme
Indicates that an action, event, or situation is associated with a central motivating theme or underlying driving idea.
-
C.
depictsMotive
chosen
Indicates that one entity visually represents or illustrates the motive, intention, or underlying reason associated with another entity or action.
-
D.
usesMuskFor
Indicates that one entity employs or applies musk (a scent or musk-derived substance) for a particular purpose involving another entity.
-
E.
usesMotto
Indicates that one entity adopts or employs a particular motto as its guiding phrase or slogan.
- 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_69e75a8fdd3881909ba0b05aa5da92a7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 21, 2026, 1:11 p.m.