Triple
T9818749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 24th Infantry Division (United States) |
E238473
|
entity |
| Predicate | inactivatedDate |
P14100
|
FINISHED |
| Object | 1996-02-15 |
—
|
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: 1996-02-15 | Statement: [24th Infantry Division (United States), inactivatedDate, 1996-02-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inactivatedDate Context triple: [24th Infantry Division (United States), inactivatedDate, 1996-02-15]
-
A.
inactivationReason
Indicates the reason or cause for which an entity, status, or process has been deactivated or made inactive.
-
B.
suspensionDate
Indicates the date on which an entity’s normal status, operation, or privileges are formally suspended.
-
C.
dateOfSuppression
Indicates the specific date on which something (such as information, a record, or a right) was formally suppressed, withheld, or made inactive.
-
D.
decayDate
Indicates the date on which something ceases to be valid, effective, or usable (i.e., when it expires or decays).
-
E.
decommissionedDate
chosen
Indicates the date on which an entity was formally taken out of service or retired from active use.
- 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_69ca84dfde1481909f47c286d715f892 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb2f74e348190be8e4394ae6fe3fe |
completed | April 2, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cd03e01ea881909a7d93fc3994ace5 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:31 p.m.