Triple
T20614842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NYSE trading calendar |
E506537
|
entity |
| Predicate | mayBeUpdatedFor |
P12017
|
FINISHED |
| Object | extraordinary market events |
—
|
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: extraordinary market events | Statement: [NYSE trading calendar, mayBeUpdatedFor, extraordinary market events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeUpdatedFor Context triple: [NYSE trading calendar, mayBeUpdatedFor, extraordinary market events]
-
A.
isUpdated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or a reference point.
-
B.
isUpdatedWhen
Indicates that one entity undergoes a change or refresh whenever another specified entity is modified or updated.
-
C.
isUpdateFor
Indicates that one entity serves as a newer or modified version that replaces or revises another entity.
-
D.
mayBeUpgradedTo
Indicates that one entity is eligible or allowed to be changed into a higher, improved, or more advanced version represented by another entity.
-
E.
mayBeModifiedBy
chosen
Indicates that an entity has the potential to be altered, changed, or updated by another entity or process.
- 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_69e0b4bc90988190ac360aaf645efc1d |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aadaf47881909e93efb535c6c1e3 |
completed | April 20, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.