Triple
T157133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ascension |
E3203
|
entity |
| Predicate | alsoObservedOn |
P5452
|
FINISHED |
| Object | the following Sunday in some regions |
—
|
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: the following Sunday in some regions | Statement: [Ascension, alsoObservedOn, the following Sunday in some regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoObservedOn Context triple: [Ascension, alsoObservedOn, the following Sunday in some regions]
-
A.
observedBy
Indicates that an entity is perceived, monitored, or recorded by another entity acting as the observer.
-
B.
observerStatusIn
Indicates that an entity’s status or role is defined or valid within a specified observational context, system, or environment.
-
C.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
D.
listedOn
Indicates that an item, entity, or piece of information appears as an entry on a particular list, platform, or catalog.
-
E.
displayedAt
Indicates that one entity is presented or exhibited at a particular location, venue, or event.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a25830136881909f5ecb2cb22097b2 |
completed | Feb. 28, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69a2565f30848190a2a71fdb7dc140b5 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a257101060819094db0f3a3a72f312 |
completed | Feb. 28, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.