Triple
T35050836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whitespring Bunker |
E1011324
|
entity |
| Predicate | preWarAffiliation |
P182491
|
FINISHED |
| Object | Enclave |
—
|
NE NERFINISHED |
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: Enclave | Statement: [Whitespring Bunker, preWarAffiliation, Enclave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preWarAffiliation Context triple: [Whitespring Bunker, preWarAffiliation, Enclave]
-
A.
affiliationDuringWar
Indicates the relationship of an entity’s formal or de facto alignment, support, or membership with a side or organization specifically during a wartime period.
-
B.
preWarCountry
Indicates that a country existed or held a particular status prior to a specified war or major armed conflict.
-
C.
initiallyAlliedWith
Indicates that two entities start out in a state of alliance or cooperation at the beginning of a specified period or scenario.
-
D.
preWarRole
Indicates the role, position, or function an entity held before the onset of a specified war or conflict.
-
E.
preWorldWarIAlignment
Indicates the political or military alliance a party belonged to before the outbreak of World War I.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78dbf72648190a4971a558e9d1889 |
completed | May 3, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78ce43094819093857fc99f269afe |
completed | May 3, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:01 p.m.