Triple
T28481136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO joint force staffs |
E720690
|
entity |
| Predicate | mayBeDeployedAs |
P85293
|
FINISHED |
| Object | standing headquarters |
—
|
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: standing headquarters | Statement: [NATO joint force staffs, mayBeDeployedAs, standing headquarters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeDeployedAs Context triple: [NATO joint force staffs, mayBeDeployedAs, standing headquarters]
-
A.
canBeDeployedUnder
Indicates that one entity is permitted or suitable to be deployed or operated under the conditions, context, or authority defined by another entity.
-
B.
canDeployAs
chosen
Indicates that one entity is capable of being deployed or instantiated in the role, form, or environment represented by another entity.
-
C.
canDeploy
Indicates that one entity has the permission or capability to deploy another entity (such as software, resources, or configurations) into a target environment.
-
D.
canDeployWith
Indicates that one entity is compatible or allowed to be deployed together with another entity in the same environment or configuration.
-
E.
isDeployedFrom
Indicates that one entity originates, is launched, or put into operation from another specified source or location.
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 28, 2026, 2:55 a.m.