Triple
T25300593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FLN militants |
E634333
|
entity |
| Predicate | facedTactic |
P48051
|
FINISHED |
| Object | collective punishment measures |
—
|
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: collective punishment measures | Statement: [FLN militants, facedTactic, collective punishment measures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facedTactic Context triple: [FLN militants, facedTactic, collective punishment measures]
-
A.
tactic
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
B.
militaryTacticsFaced
chosen
Indicates that an entity encountered or had to contend with specific military tactics employed by another entity.
-
C.
facedBy
Indicates that one entity is oriented toward and directly opposite another entity, such that it is facing it.
-
D.
describedTactic
Indicates that one entity has provided an explanation or account of a particular tactic used or proposed by another entity.
-
E.
tacticalFeatureUsed
Indicates that a specific tactical feature, maneuver, or capability is employed or brought into play within a tactical situation or operation.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48fd66d50819095c3d24c7065c351 |
completed | May 1, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:24 p.m.