Triple
T2306921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keys of Heaven |
E51860
|
entity |
| Predicate | goldKeySymbolizes |
P7657
|
FINISHED |
| Object | power in 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: power in heaven | Statement: [Keys of Heaven, goldKeySymbolizes, power in heaven]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goldKeySymbolizes Context triple: [Keys of Heaven, goldKeySymbolizes, power in heaven]
-
A.
keySymbol
chosen
Indicates that one entity serves as the symbolic representation or notation used to denote another entity as a key.
-
B.
standardGoldContent
Indicates the specified standard or required amount of gold contained in something, typically as a measure of purity or value.
-
C.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
D.
keySaying
Indicates that an entity is a notable or characteristic saying, phrase, or quotation associated with another entity.
-
E.
keyMetaphor
Indicates that one entity functions as a central or primary metaphor used to conceptualize, explain, or structure understanding of 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_69a88b0bb30c81908ded03b006d29387 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abce1f4f0c8190a714e4dcb8449f7e |
completed | March 7, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69abc58ce2a081908ce2f0cadd92e9f8 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.