Triple
T6550144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Thailand insurgency |
E151108
|
entity |
| Predicate | targetsInclude |
P61966
|
FINISHED |
| Object | security forces |
—
|
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: security forces | Statement: [South Thailand insurgency, targetsInclude, security forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsInclude Context triple: [South Thailand insurgency, targetsInclude, security forces]
-
A.
targetsUseCase
Indicates that one entity is aimed at or designed to address a particular use case associated with another entity.
-
B.
usesTarget
Indicates that one entity employs, applies, or operates on another entity as its target or object of action.
-
C.
targetsShow
Indicates that one entity is the intended audience or focus of a particular show or presentation.
-
D.
intendedTargets
chosen
Indicates that an action, message, or object is specifically directed toward or meant to affect particular target entities.
-
E.
includesSee
Indicates that one entity’s scope, content, or experience contains or encompasses the act of seeing or visual perception involving 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_69c687f3fd60819083bfa583e5bcfa71 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce07332481909a5a7964282eb776 |
completed | March 27, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69c6acf3e3708190b052ec774e607cb7 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:51 p.m.