Triple
T37592676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perdition Hold |
E935297
|
entity |
| Predicate | regionLanguageName_enUS |
P52154
|
FINISHED |
| Object | Perdition Hold |
—
|
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: Perdition Hold | Statement: [Perdition Hold, regionLanguageName_enUS, Perdition Hold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionLanguageName_enUS Context triple: [Perdition Hold, regionLanguageName_enUS, Perdition Hold]
-
A.
regionLanguage
Indicates that a particular language is used or officially recognized within a specific geographic region.
-
B.
localLanguageName
chosen
Indicates the name of a language as it is written or referred to in its own local or native form.
-
C.
subjectLanguageRegion
Indicates that the subject is associated with or uses a language specific to a particular geographic region.
-
D.
regionLanguageType
Indicates the type or category of language associated with a given region.
-
E.
standardLanguageOf
Indicates that one entity serves as the officially recognized or commonly used standard language for another entity (such as a country, region, or organization).
- 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00694f72888190983fee7d687a6daa |
completed | May 10, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_6a00685dbf44819098ea0c86bb9e50d8 |
completed | May 10, 2026, 11:13 a.m. |
Created at: May 3, 2026, 4:18 p.m.