Triple
T14690128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Stallion |
E345013
|
entity |
| Predicate | religiousMotto |
P63665
|
FINISHED |
| Object | “It is known” (associated Dothraki affirmation) |
—
|
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: “It is known” (associated Dothraki affirmation) | Statement: [Great Stallion, religiousMotto, “It is known” (associated Dothraki affirmation)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousMotto Context triple: [Great Stallion, religiousMotto, “It is known” (associated Dothraki affirmation)]
-
A.
isReligiousMotto
chosen
Indicates that a phrase functions as a religious motto, expressing a faith-based guiding principle or belief.
-
B.
scripturalMotto
Indicates that one entity serves as the official scriptural or religiously inspired motto or guiding phrase associated with another entity.
-
C.
isMottoOf
Indicates that a phrase or expression serves as the official motto associated with a particular entity.
-
D.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
-
E.
mottoInterpretation
Indicates the explanatory relationship between a motto and its intended meaning or message.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb5844de481908a796eaa474bfde9 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.