Triple
T10770692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corpus Hermeticum |
E254065
|
entity |
| Predicate | earlierPerceivedDate |
P64188
|
FINISHED |
| Object | belief in extreme antiquity before Moses |
—
|
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: belief in extreme antiquity before Moses | Statement: [Corpus Hermeticum, earlierPerceivedDate, belief in extreme antiquity before Moses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierPerceivedDate Context triple: [Corpus Hermeticum, earlierPerceivedDate, belief in extreme antiquity before Moses]
-
A.
earliestDate
chosen
Indicates the earliest point in time at which an associated event, state, or relationship is considered to begin or be valid.
-
B.
createdBefore
Indicates that one entity was created at an earlier time than another entity.
-
C.
firstReachedDate
Indicates the date on which a particular entity first achieved, accessed, or arrived at a specified state, location, or milestone.
-
D.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
-
E.
observedSince
Indicates that one entity has been continuously or repeatedly observed starting from a specified point in time.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d732314bcc8190980c6f698f64ccf5 |
completed | April 9, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69d6f31455648190b5c24690487b1b54 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:16 p.m.