Triple
T15041830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lohamei Herut Israel |
E378616
|
entity |
| Predicate | positionOnWorldWarII |
P19660
|
FINISHED |
| Object | anti-British even during World War II |
—
|
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: anti-British even during World War II | Statement: [Lohamei Herut Israel, positionOnWorldWarII, anti-British even during World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnWorldWarII Context triple: [Lohamei Herut Israel, positionOnWorldWarII, anti-British even during World War II]
-
A.
sideInWorldWarII
Indicates that an entity was aligned with or participated on a particular side during World War II.
-
B.
statusDuringWorldWarII
chosen
Indicates the role, condition, or classification an entity had specifically during the period of World War II.
-
C.
positionOnWorldWarI
Indicates a person’s or group’s stance, opinion, or policy regarding World War I.
-
D.
WWIITheater
Indicates the geographic or operational theater in which a World War II-related event, action, or entity was involved.
-
E.
higherCommandDuringWWII
Indicates that one entity served as the superior military authority or command over another entity during 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded82f73208190bb55fa6b20074e27 |
completed | April 15, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69de9a69d7848190b2b4662dd30f20e9 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 3 a.m.