Triple
T32080344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mobile Task Force |
E819274
|
entity |
| Predicate | mayBeTaskedWith |
P109416
|
FINISHED |
| Object | area security |
—
|
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: area security | Statement: [Mobile Task Force, mayBeTaskedWith, area security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeTaskedWith Context triple: [Mobile Task Force, mayBeTaskedWith, area security]
-
A.
isTaskedWith
chosen
Indicates that an entity has been assigned the responsibility or duty to perform a specific task or set of tasks.
-
B.
canBeAssignedTo
Indicates that one entity is eligible or permitted to be allocated, designated, or linked to another entity for a particular purpose or role.
-
C.
mayBeDelegatedTo
Indicates that a responsibility, task, or authority can be transferred from one entity to another to act on its behalf.
-
D.
canBeTaskOrganizedWith
Indicates that one entity can be grouped, scheduled, or managed together with another as part of the same task or workflow.
-
E.
canTask
Indicates that an entity has the ability or permission to perform a specified task.
- 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: May 1, 2026, 12:24 a.m.