Triple
T13597060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 11th Airborne Division |
E324848
|
entity |
| Predicate | historicalActivation |
P110228
|
FINISHED |
| Object | 1943 |
—
|
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: 1943 | Statement: [11th Airborne Division, historicalActivation, 1943]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalActivation Context triple: [11th Airborne Division, historicalActivation, 1943]
-
A.
historicActivity
Indicates that an entity engaged in an activity or event of historical significance in the past.
-
B.
historicallyActiveIn
Indicates that an entity was active or engaged in significant activities within a particular place or context during a past historical period.
-
C.
historicalStatusOf
Indicates the historical condition, role, or classification that an entity held during a specific past period or context.
-
D.
estimatedHistory
Indicates that there is an inferred or approximated record of past states, events, or values associated with an entity or relationship.
-
E.
historicalPass
Indicates that an entity has successfully completed or passed a historical event, period, or examination related to history.
- F. None of above. chosen
Provenance (4 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb0590558819080ccc5874a650b1e |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbaf9f3bdc8190838539aaef1f422b |
completed | April 12, 2026, 2:43 p.m. |
Created at: April 9, 2026, 9:49 p.m.