Triple
T7116931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XVIII Airborne Corps Artillery |
E165842
|
entity |
| Predicate | inactivationDate |
P14100
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [XVIII Airborne Corps Artillery, inactivationDate, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inactivationDate Context triple: [XVIII Airborne Corps Artillery, inactivationDate, 2006]
-
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.
ceaseToExistDecisionDate
Indicates the date on which a formal decision was made that something will cease to exist or be terminated.
-
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_69c6888227bc8190a1394679e3116f90 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e617a528819085d4b8e1b5699966 |
completed | March 27, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c4f9788190830288d00cc37026 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.