Triple
T23973423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | START II |
E604296
|
entity |
| Predicate | RussianSuspensionAnnouncementDate |
P38380
|
FINISHED |
| Object | 2002-06-14 |
—
|
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: 2002-06-14 | Statement: [START II, RussianSuspensionAnnouncementDate, 2002-06-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RussianSuspensionAnnouncementDate Context triple: [START II, RussianSuspensionAnnouncementDate, 2002-06-14]
-
A.
suspensionDate
chosen
Indicates the date on which an entity’s normal status, operation, or privileges are formally suspended.
-
B.
suspensionReason
Indicates the reason or cause for which an entity has been suspended from a status, activity, or service.
-
C.
hasSuspension
Indicates that one entity is subject to a temporary suspension imposed or recorded by another entity.
-
D.
suspension
Indicates the temporary removal or halting of a privilege, activity, or status for an entity, often as a consequence or precaution.
-
E.
suspendedFrom
Indicates that one entity is hanging or held up in the air by being attached to another supporting entity.
- 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_69e29543019c8190872462e593cc50b4 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d1dda91c8190af716bceb3225aee |
completed | April 29, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:25 p.m.