Triple
T35119511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faith of the Seven High Septon |
E1014127
|
entity |
| Predicate | canCrown |
P182548
|
FINISHED |
| Object | kings of the Seven Kingdoms |
—
|
NE NERFINISHED |
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: kings of the Seven Kingdoms | Statement: [Faith of the Seven High Septon, canCrown, kings of the Seven Kingdoms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canCrown Context triple: [Faith of the Seven High Septon, canCrown, kings of the Seven Kingdoms]
-
A.
crownedWith
Indicates that one entity serves as a crown, top, or decorative upper covering placed upon another entity.
-
B.
hasCrownName
Indicates that an entity possesses or is identified by a specific crown name, typically used as an official or regal title.
-
C.
hasCrownGroup
Indicates that an entity belongs to, or is classified within, the crown group (the clade consisting of a common ancestor and all its living descendants) of another specified lineage or taxonomic group.
-
D.
hasCrownCount
Indicates the number of crowns that an entity possesses or is associated with.
-
E.
crownPresent
Indicates that a crown is currently present on or with the relevant entity.
- F. None of above. chosen
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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78dbf72648190a4971a558e9d1889 |
completed | May 3, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78ce43094819093857fc99f269afe |
completed | May 3, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:01 p.m.