Triple
T36793148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Ridge Division |
E909107
|
entity |
| Predicate | enteredCombatInWorldWarII |
P128995
|
FINISHED |
| Object | 1944 |
—
|
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: 1944 | Statement: [Blue Ridge Division, enteredCombatInWorldWarII, 1944]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredCombatInWorldWarII Context triple: [Blue Ridge Division, enteredCombatInWorldWarII, 1944]
-
A.
sideInWorldWarII
Indicates that an entity was aligned with or participated on a particular side during World War II.
-
B.
sawCombatAfterWWII
Indicates that the entity participated in or experienced military combat operations occurring after the end of World War II.
-
C.
hasWorldWarIIAssociation
Indicates that there is a notable connection or relevance between an entity and World War II, such as involvement, impact, or contextual association.
-
D.
worldWarIIEntry
chosen
Indicates that an entity’s formal involvement or entry into World War II is being asserted in relation to a specific time, event, or condition.
-
E.
duringWorldWar
Indicates that one entity’s action, state, or relationship occurred within the temporal span of World War II.
- 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:12 p.m.