Triple
T20079317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eternal Word |
E499955
|
entity |
| Predicate | isPreExistent |
P56217
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Eternal Word, isPreExistent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPreExistent Context triple: [Eternal Word, isPreExistent, true]
-
A.
existedAfter
Indicates that one entity came into existence only after another entity already existed.
-
B.
existedBeforeEvent
chosen
Indicates that the subject entity was already in existence prior to the occurrence of the specified event.
-
C.
existedAs
Indicates that one entity had the status, form, or identity of another entity during a certain time or context.
-
D.
previouslyEstablished
Indicates that the relationship or condition it connects has already been formed or confirmed at an earlier time before the current context.
-
E.
hasExistenceStatus
Indicates that an entity is associated with a particular state of existence, such as being current, historical, planned, or no longer existing.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6643f93208190ae2a413f88ea9aed |
completed | April 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:40 p.m.