Triple
T37471845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hibernal Hollow |
E931171
|
entity |
| Predicate | cosmicPlane |
P123519
|
FINISHED |
| Object | Shadowlands |
E273800
|
NE 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: Shadowlands | Statement: [Hibernal Hollow, cosmicPlane, Shadowlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cosmicPlane Context triple: [Hibernal Hollow, cosmicPlane, Shadowlands]
-
A.
cosmicCenter
Indicates that one entity serves as the central or focal point around which other cosmic entities or structures are organized or defined.
-
B.
cosmicDimension
chosen
Indicates a relationship where something exists, operates, or is characterized within a particular cosmic or universal scale, realm, or dimension.
-
C.
cosmicForm
Indicates a relationship where an entity manifests, assumes, or is represented in a vast, universal, or transcendent cosmic form.
-
D.
cosmicDirection
Indicates the orientation or path of something relative to a larger cosmic or celestial frame of reference.
-
E.
cosmicBoundary
Indicates a relationship where something marks, defines, or lies at the outermost limit or edge of a cosmic region, domain, or structure.
- F. None of above.
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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a415d12d0548190b0102321d381c2ac |
completed | June 28, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.