Triple
T3007233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allied Joint Force Command Brunssum |
E81931
|
entity |
| Predicate | headquartersType |
P4474
|
FINISHED |
| Object | operational-level 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: operational-level headquarters | Statement: [Allied Joint Force Command Brunssum, headquartersType, operational-level headquarters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headquartersType Context triple: [Allied Joint Force Command Brunssum, headquartersType, operational-level headquarters]
-
A.
headquartersFunction
Indicates that an entity serves as the main administrative or central operating location (headquarters) for another entity.
-
B.
hasHeadquartersType
chosen
Indicates the specific kind or classification of headquarters associated with an entity.
-
C.
headquartersMunicipality
Indicates the municipality in which an organization’s main administrative headquarters is located.
-
D.
headquartersFor
Indicates that a location serves as the main administrative center or base of operations for an organization or entity.
-
E.
headquartersLocation
Indicates the place where an organization’s main administrative center or principal office is located.
- 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_69ad8b1c4de88190a83b7cefaa1f2842 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a4a12508190a48ae1c86233d25e |
completed | March 8, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69ad96180eb08190a524c5f458d41382 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.