Triple
T6895945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palmach |
E159169
|
entity |
| Predicate | initialPurpose |
P63932
|
FINISHED |
| Object | defense against possible Axis invasion |
—
|
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: defense against possible Axis invasion | Statement: [Palmach, initialPurpose, defense against possible Axis invasion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialPurpose Context triple: [Palmach, initialPurpose, defense against possible Axis invasion]
-
A.
purpose
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
-
B.
initialGoal
chosen
Indicates that something represents the first or starting objective or target in a sequence of goals.
-
C.
hasOriginalEndowmentPurpose
Indicates that an entity’s original endowment is intended or designated to serve a specific purpose or function.
-
D.
reasonForUse
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
-
E.
purposeOfConstruction
Indicates that one entity was constructed or built in order to serve, enable, or fulfill the function, goal, or intended use represented by another entity.
- 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_69c6883568c8819081db6407e892cccc |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d95ae3f88190b7f5d440f90ae9f9 |
completed | March 27, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:24 p.m.