Triple
T13273261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Task Force 51 |
E316120
|
entity |
| Predicate | isRapidlyDeployable |
P47943
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Task Force 51, isRapidlyDeployable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRapidlyDeployable Context triple: [Task Force 51, isRapidlyDeployable, true]
-
A.
isRapidReactionUnit
Indicates that an entity functions as a unit specifically organized, trained, and equipped to respond quickly to emerging situations or emergencies.
-
B.
canDeploy
Indicates that one entity has the permission or capability to deploy another entity (such as software, resources, or configurations) into a target environment.
-
C.
canBeMobilisedFor
chosen
Indicates that an entity is capable of being called upon, activated, or deployed for a particular purpose, task, or operation.
-
D.
canDeployAs
Indicates that one entity is capable of being deployed or instantiated in the role, form, or environment represented by another entity.
-
E.
canDeployWithin
Indicates that one entity has the capability or permission to be deployed inside or within the scope, boundary, or environment defined 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:26 p.m.