Triple
T528493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AOL Instant Messenger |
E10976
|
entity |
| Predicate | serviceShutdownDate |
P6603
|
FINISHED |
| Object | December 15, 2017 |
—
|
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: December 15, 2017 | Statement: [AOL Instant Messenger, serviceShutdownDate, December 15, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceShutdownDate Context triple: [AOL Instant Messenger, serviceShutdownDate, December 15, 2017]
-
A.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
-
B.
operatedUntil
chosen
Indicates that an entity continued to function or be in operation up to a specified end time or date.
-
C.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
-
D.
surrenderDate
Indicates the date on which an entity formally yields control, possession, or rights, typically ending its claim or resistance.
-
E.
withdrawalDate
Indicates the date on which a withdrawal action occurs or is recorded.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1d39b4c81909f265b3501b5ec1d |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f01ac3ec8190a94a05955532c7fa |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.