Triple
T2001051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fedayeen |
E43470
|
entity |
| Predicate | typicalTargets |
P10541
|
FINISHED |
| Object | military targets |
—
|
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: military targets | Statement: [Fedayeen, typicalTargets, military targets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTargets Context triple: [Fedayeen, typicalTargets, military targets]
-
A.
primaryTargetType
Indicates the main category or type of entity that is the principal focus or intended recipient of an action, effect, or operation.
-
B.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
C.
typicalFeatures
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
-
D.
typicalTargetIncrement
Indicates the usual or expected amount by which a target value is intended to increase in a given adjustment or period.
-
E.
targetsGroup
chosen
Indicates that an action, influence, or effect is directed toward a specific group as its intended recipient or focus.
- 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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb880c710819098fb877052ce56dc |
completed | March 7, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69abb79e63c08190982c8b44a557266f |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.