Triple
T34797597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunmer |
E1003132
|
entity |
| Predicate | greatHouse |
P115449
|
FINISHED |
| Object | House Redoran |
—
|
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: House Redoran | Statement: [Dunmer, greatHouse, House Redoran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: greatHouse Context triple: [Dunmer, greatHouse, House Redoran]
-
A.
associatedGreatHouse
chosen
Indicates that one entity is linked or connected to a particular great house, typically by affiliation, allegiance, or origin.
-
B.
chiefHouse
Indicates that a particular house serves as the primary or leading residence associated with a given entity (such as a person, group, or organization).
-
C.
countryHouse
Indicates that a given house is located within or belongs to a particular country.
-
D.
eraOfMainHouse
Indicates the historical period or architectural era during which the main house was originally built or primarily developed.
-
E.
houseFounded
Indicates that an entity (such as a house, organization, or lineage) was established or created by another entity or at a specific time.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77a86050881909fa363fe6984f79f |
completed | May 3, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_69f7795b1abc8190823664d1caa94649 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.