Triple
T29577032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P 4 |
E753470
|
entity |
| Predicate | basedAtMilitaryInstallation |
P73931
|
FINISHED |
| Object | Skövde garrison |
—
|
NE NERFINISHED |
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: Skövde garrison | Statement: [P 4, basedAtMilitaryInstallation, Skövde garrison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedAtMilitaryInstallation Context triple: [P 4, basedAtMilitaryInstallation, Skövde garrison]
-
A.
locatedOnMilitaryInstallation
chosen
Indicates that one entity is physically situated within the boundaries of, or directly on, a military installation or base.
-
B.
formerlyLocatedOnMilitaryInstallation
Indicates that an entity was previously situated on a military installation but is no longer located there.
-
C.
isMilitaryInstallation
Indicates that a location functions as a military facility or base used for defense, training, operations, or related armed forces activities.
-
D.
isMilitaryBranchInstallationOf
Indicates that a specific military installation belongs to, is operated by, or is an official facility of a particular military branch.
-
E.
hasFormerMilitaryInstallationNearby
Indicates that an entity is located close to a site where a military installation previously existed but is no longer active.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: April 28, 2026, 6:03 p.m.