Triple
T3487850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lehi |
E73651
|
entity |
| Predicate | initiallyPositionedAs |
P49062
|
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: [Lehi, initiallyPositionedAs, anti-British even during World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initiallyPositionedAs Context triple: [Lehi, initiallyPositionedAs, anti-British even during World War II]
-
A.
positionedAgainst
Indicates that one entity is placed so that it directly faces or is set opposite to another entity, often in close or contacting alignment.
-
B.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
C.
positionA
Indicates the spatial or ordered position of an entity A within a defined reference frame or sequence.
-
D.
positioning
Indicates the spatial or contextual arrangement of one entity relative to another or within a given environment.
-
E.
positionEstablishedIn
Indicates the point in time or event when a particular position, role, or office was formally created or instituted.
- 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_69ad85cca8d4819088494e9f3340fab5 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbb9193688190aa0cbf87a7b99446 |
completed | March 8, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69adae0935ac8190bfa8a8bd3dcd3301 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb1ecb02881908394f197e31431b4 |
completed | March 8, 2026, 5:29 p.m. |
Created at: March 8, 2026, 3:18 p.m.