Triple
T18301369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yahoo! Answers |
E438364
|
entity |
| Predicate | announcementOfShutdownDate |
P128529
|
FINISHED |
| Object | 2021-04-05 |
—
|
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: 2021-04-05 | Statement: [Yahoo! Answers, announcementOfShutdownDate, 2021-04-05]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcementOfShutdownDate Context triple: [Yahoo! Answers, announcementOfShutdownDate, 2021-04-05]
-
A.
finalShutdownDate
Indicates the date on which an entity is permanently shut down or ceases operation.
-
B.
permanentClosureAnnouncementDate
Indicates the date on which an official announcement was made that something (such as a facility, service, or location) will be permanently closed.
-
C.
shutdownAnnouncedOn
chosen
Indicates that an official announcement was made on a specific date or platform that a system, service, or operation will be shut down.
-
D.
announcementDate
Indicates the date on which an announcement is formally made or becomes publicly known.
-
E.
announcedPermanentClosure
Indicates that an entity has formally stated that it will cease operations or availability indefinitely and not reopen.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5017f63dc819083a675d570620f2f |
completed | April 19, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.