Triple
T8707879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noÿs Lambent |
E206693
|
entity |
| Predicate | impactOnEternity |
P67693
|
FINISHED |
| Object | contributes to the end of Eternity as an institution |
—
|
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: contributes to the end of Eternity as an institution | Statement: [Noÿs Lambent, impactOnEternity, contributes to the end of Eternity as an institution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactOnEternity Context triple: [Noÿs Lambent, impactOnEternity, contributes to the end of Eternity as an institution]
-
A.
impactEvent
Indicates that one entity physically strikes or collides with another, producing a resulting effect or change.
-
B.
impactOrigin
Indicates that one entity is the source or cause from which the impact or effect on another entity originates.
-
C.
التأثير
chosen
Indicates a relationship where one entity produces a change or has an influence on another entity or its state.
-
D.
impactBuilding
Indicates that one entity physically collides with or strikes a building, causing an impact event.
-
E.
impactIfCompleted
Indicates the effect or consequence that will occur if the referenced task or action is fully completed.
- 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_69ca835645e881908f00e3c8b51da81d |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc58ffa6a481908866b6239d1d9b92 |
completed | March 31, 2026, 11:30 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.