Triple
T10734759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vesper |
E253164
|
entity |
| Predicate | seenAfter |
P95708
|
FINISHED |
| Object | sunset |
—
|
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: sunset | Statement: [Vesper, seenAfter, sunset]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seenAfter Context triple: [Vesper, seenAfter, sunset]
-
A.
seenFrom
Indicates that one entity is visible or can be observed from the vantage point or location of another entity.
-
B.
coveredSince
Indicates that one entity has been under the protection, applicability, or effect of another entity continuously starting from a specified point in time.
-
C.
hasSee
Indicates that one entity has perceived or visually observed another entity.
-
D.
previouslyObserved
Indicates that the subject entity has been seen, recorded, or encountered at some earlier time prior to the current context.
-
E.
usedSince
Indicates that an entity has been in use starting from a specified point in time and continuing thereafter.
- F. None of above. chosen
Provenance (4 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d71020e1c881909e40f398de2bdd25 |
completed | April 9, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69d6f309a44881908e49e3ba478c35b4 |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa323564819097b207eb53f8a9b8 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:14 p.m.