Triple
T24517612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort George, Highland, Scotland |
E606417
|
entity |
| Predicate | stillInMilitaryUse |
P23907
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Fort George, Highland, Scotland, stillInMilitaryUse, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stillInMilitaryUse Context triple: [Fort George, Highland, Scotland, stillInMilitaryUse, yes]
-
A.
eraOfPrimaryMilitaryUse
Indicates the historical time period during which the subject was primarily used for military purposes.
-
B.
militaryUse
chosen
Indicates the use of something (such as land, facilities, equipment, or resources) for military purposes or operations.
-
C.
isMilitaryAssetOf
Indicates that something functions as a military resource, equipment, or facility that belongs to, is controlled by, or is used by a particular entity.
-
D.
postMilitaryUse
Indicates that an entity is used or repurposed after its original military function or service has ended.
-
E.
hasMilitaryType
Indicates that an entity is associated with or classified under a specific military category, role, or type.
- 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_69e2c4c85778819085f5da9af3569ad5 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:24 a.m.