Triple
T33212241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 99942 Apophis |
E850190
|
entity |
| Predicate | removedFromSentryRiskTableDate |
P176197
|
FINISHED |
| Object | 2021-03-26 |
—
|
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-03-26 | Statement: [99942 Apophis, removedFromSentryRiskTableDate, 2021-03-26]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: removedFromSentryRiskTableDate Context triple: [99942 Apophis, removedFromSentryRiskTableDate, 2021-03-26]
-
A.
removedFromSentryRiskTable
chosen
Indicates that an entity has been deleted or excluded from the Sentry risk assessment table or listing.
-
B.
burdenRemovedAt
Indicates the time or event at which a previously existing burden, obligation, or constraint is lifted or no longer applies.
-
C.
removalStartDate
Indicates the date on which the process of removing an entity or item is initiated.
-
D.
removedOn
Indicates that an entity was taken away, deleted, or detached at a specific point in time.
-
E.
dateOfExfiltration
Indicates the specific date on which data or information was illicitly removed or extracted from its original location.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:30 a.m.