Triple
T29716827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 462d Bombardment Group |
E751932
|
entity |
| Predicate | disbandedOrInactivatedDate |
P62226
|
FINISHED |
| Object | 1946-03-31 |
—
|
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: 1946-03-31 | Statement: [462d Bombardment Group, disbandedOrInactivatedDate, 1946-03-31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disbandedOrInactivatedDate Context triple: [462d Bombardment Group, disbandedOrInactivatedDate, 1946-03-31]
-
A.
disbandedAt
chosen
Indicates the time or date at which an organized group, body, or entity formally ceased to exist or operate.
-
B.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
-
C.
disbandedDuring
Indicates that an entity ceased to exist or was formally dissolved at some point within the duration of a specified event or time period.
-
D.
decommissioningEndDate
Indicates the date on which a decommissioning process or status for something is completed or officially ends.
-
E.
decommissioningStartDate
Indicates the date on which the process of taking an asset or system out of active service is initiated.
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672dd9ab881908969657a9bd48098 |
completed | May 2, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:34 p.m.