Triple
T24517628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort George, Highland, Scotland |
E606417
|
entity |
| Predicate | hasMagazine |
P156588
|
FINISHED |
| Object | gunpowder magazines |
—
|
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: gunpowder magazines | Statement: [Fort George, Highland, Scotland, hasMagazine, gunpowder magazines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMagazine Context triple: [Fort George, Highland, Scotland, hasMagazine, gunpowder magazines]
-
A.
hasMagazineType
Indicates that an entity is associated with, or classified by, a specific type or category of magazine.
-
B.
hasChamber
Indicates that one entity possesses, contains, or is associated with a distinct enclosed space or compartment (a chamber).
-
C.
positionInMagazine
Indicates that one entity occupies a specific location or slot within a magazine (such as an ordered container or publication).
-
D.
hasChamberStatus
Indicates that an entity holds a particular status or condition within a specific chamber or legislative body.
-
E.
hasBarrel
Indicates that one entity possesses, includes, or is equipped with a barrel as a component or feature.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f2a9d795288190916368e3cec1f666 |
completed | April 30, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:24 a.m.