Triple
T25289816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of the Mysterious Region |
E634048
|
entity |
| Predicate | epithetOfDomain |
P104657
|
FINISHED |
| Object | hidden regions |
—
|
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: hidden regions | Statement: [Lord of the Mysterious Region, epithetOfDomain, hidden regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: epithetOfDomain Context triple: [Lord of the Mysterious Region, epithetOfDomain, hidden regions]
-
A.
epithetScope
chosen
Indicates that an epithet (a descriptive label or phrase) applies specifically within a defined contextual scope or domain for the referenced entity or relation.
-
B.
epithetAppliedBy
Indicates that a particular epithet or descriptive label is used or assigned by a specific agent to a target entity.
-
C.
epithetOfOwner
Indicates that a descriptive epithet or nickname is associated with and refers specifically to the owner of an entity.
-
D.
languageOfEpithet
Indicates the language in which an epithet (such as a descriptive or honorary title) is expressed.
-
E.
epithetOrTitle
Indicates that one entity serves as an epithet, honorific, or formal title used to designate or characterize another entity.
- 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48e0c2aa88190aca9e47be7138854 |
completed | May 1, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:21 p.m.