Triple
T967897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seven Seals |
E20877
|
entity |
| Predicate | locationInText |
P1637
|
FINISHED |
| Object | heavenly throne room vision |
—
|
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: heavenly throne room vision | Statement: [Seven Seals, locationInText, heavenly throne room vision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationInText Context triple: [Seven Seals, locationInText, heavenly throne room vision]
-
A.
locationInDocument
chosen
Indicates that one entity specifies where another entity is situated or referenced within a document.
-
B.
locationOfPassage
Indicates the place or area through which a passage, route, or transit occurs or is situated.
-
C.
leftLocation
Indicates that an entity has departed from or moved away from a specified location.
-
D.
locationDescription
Indicates a textual description that specifies or characterizes the location of an entity.
-
E.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
- 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b43549008190a4d65efdc3bda520 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a42c1481908d940cbe0aefdd3b |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.