Triple
T37551072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trial of the Crusader |
E933590
|
entity |
| Predicate | primaryLoreTheme |
P150352
|
FINISHED |
| Object | Argent Tournament trials |
E2230416
|
NE 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: Argent Tournament trials | Statement: [Trial of the Crusader, primaryLoreTheme, Argent Tournament trials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryLoreTheme Context triple: [Trial of the Crusader, primaryLoreTheme, Argent Tournament trials]
-
A.
primaryStoryThemes
chosen
Indicates the main recurring ideas or motifs that characterize and unify a story’s narrative.
-
B.
primaryFunctionInLore
Indicates that something’s main role or purpose is defined within a fictional or narrative lore context.
-
C.
centralMythology
Indicates that one entity serves as a core or defining mythological element within the context or tradition of another entity.
-
D.
taleTheme
Indicates that a tale centers around, conveys, or is primarily associated with a particular theme.
-
E.
loreType
Indicates the category or kind of lore that characterizes or classifies a given entity or subject.
- F. None of above.
Provenance (4 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40a7ec19c0819085d68adc48bf3ed9 |
completed | June 28, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.