Triple
T8499719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WrestleMania 37 |
E201183
|
entity |
| Predicate | hadRainDelay |
P83070
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [WrestleMania 37, hadRainDelay, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadRainDelay Context triple: [WrestleMania 37, hadRainDelay, yes]
-
A.
delayedBy
Indicates that one event, process, or action occurs later than expected or planned due to the influence or interference of another factor or entity.
-
B.
mayDelay
Indicates that one entity has the potential or permission to cause a postponement or slowing of another entity, event, or process.
-
C.
heldOver
Indicates that something has been continued, carried forward, or extended in effect or duration beyond its original or expected time.
-
D.
hasShowers
Indicates that one entity provides or is equipped with shower facilities for use by another entity or by people in general.
-
E.
hadNo
Indicates that one entity completely lacked or did not possess another entity, attribute, or relationship.
- 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_69ca831fe47c8190b5c57b456d2aefa0 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe5984d7481908c41c57bef9cf254 |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:14 p.m.