Triple
T22876201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fortress |
E567331
|
entity |
| Predicate | endOfActiveDevelopmentAnnouncement |
P73439
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [Fortress, endOfActiveDevelopmentAnnouncement, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfActiveDevelopmentAnnouncement Context triple: [Fortress, endOfActiveDevelopmentAnnouncement, 2012]
-
A.
endOfExtendedSupport
Indicates the point in time when extended support for something (such as a product or service) is officially terminated.
-
B.
endOfLife
Indicates that an entity has reached the termination point of its existence, lifecycle, or functional use.
-
C.
developmentEnded
chosen
Indicates that the process of creating, improving, or expanding something has been completed and no further development is taking place.
-
D.
announcedEnd
Indicates that an entity has publicly declared or made known the termination or conclusion of something.
-
E.
endOfSupportApprox
Indicates that the support period for something is expected to end around a particular time, but the exact end date is approximate rather than precise.
- 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_69e24589d8348190b96422d13a678bc1 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f58a7308190b710bdf013e2e114 |
completed | April 29, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69eed2d8c0608190afef4c4e530c0e2c |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:39 p.m.