Triple
T11579858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Heaven |
E274596
|
entity |
| Predicate | celestialDomain |
P41871
|
FINISHED |
| Object | heaven |
—
|
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: heaven | Statement: [Lord of Heaven, celestialDomain, heaven]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: celestialDomain Context triple: [Lord of Heaven, celestialDomain, heaven]
-
A.
celestialHierarchy
Indicates a ranked or ordered relationship among celestial entities, where some hold higher or more authoritative positions than others.
-
B.
celestialLocation
Indicates the spatial or positional relationship of an entity relative to a celestial body or region in space.
-
C.
cosmicDomainAssociation
Indicates an association where one entity is linked to, belongs within, or is governed by a particular cosmic or universal domain.
-
D.
cosmicSymbolism
Indicates a relationship where one entity symbolically represents or embodies cosmic, universal, or celestial principles in relation to another.
-
E.
cosmologicalRealm
chosen
Indicates that one entity exists in, belongs to, or is associated with a particular cosmological realm or plane of existence relative to another.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8904b46288190890ecafd6ceb0c3d |
completed | April 10, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.