Triple
T15802285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astronomical Book |
E383125
|
entity |
| Predicate | presentsAs |
P24836
|
FINISHED |
| Object | revelation to Enoch |
—
|
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: revelation to Enoch | Statement: [Astronomical Book, presentsAs, revelation to Enoch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentsAs Context triple: [Astronomical Book, presentsAs, revelation to Enoch]
-
A.
appearsAs
chosen
Indicates that one entity is presented, perceived, or manifested in the form, role, or guise of another entity.
-
B.
presentedBy
Indicates that something (such as an event, performance, or work) is formally organized, hosted, or introduced by a particular person or entity.
-
C.
representsAs
Indicates that one entity serves as a depiction, symbol, or stand-in for another entity in some representational context.
-
D.
originallyPresentedAs
Indicates that one entity was first introduced, described, or characterized in the form or manner specified by another entity.
-
E.
presentedFor
Indicates that one entity was formally offered, submitted, or shown to another entity for consideration, review, or action.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b523bf508190af4a54bdc983a9a1 |
completed | April 16, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:48 a.m.