Triple
T38590686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miqo'te |
E932445
|
entity |
| Predicate | hasHomeRegionInLore |
P109542
|
FINISHED |
| Object | Ilsabard |
—
|
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: Ilsabard | Statement: [Miqo'te, hasHomeRegionInLore, Ilsabard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeRegionInLore Context triple: [Miqo'te, hasHomeRegionInLore, Ilsabard]
-
A.
hasHomeRegionHistorical
Indicates that an entity is historically associated with or originates from a particular home region.
-
B.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
C.
hasMythologicalRegion
Indicates a relationship where something is associated with, set in, or belonging to a specific mythological or legendary region.
-
D.
culturalRegionOfLore
chosen
Indicates that a particular cultural region is the primary setting, origin, or contextual background for a given body of lore or tradition.
-
E.
hasHeritageRegion
Indicates that an entity is associated with, originates from, or is culturally linked to a specific heritage region.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
Created at: May 3, 2026, 4:32 p.m.