Triple
T28604306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2nd Regiment, Royal Canadian Horse Artillery |
E724000
|
entity |
| Predicate | hasGarrisonBase |
P1869
|
FINISHED |
| Object | Garrison Petawawa |
—
|
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: Garrison Petawawa | Statement: [2nd Regiment, Royal Canadian Horse Artillery, hasGarrisonBase, Garrison Petawawa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGarrisonBase Context triple: [2nd Regiment, Royal Canadian Horse Artillery, hasGarrisonBase, Garrison Petawawa]
-
A.
hasFortressConstructed
Indicates that a fortress has been built or established for, by, or at the associated entity.
-
B.
garrisonOrHQ
Indicates that an entity serves as a military garrison or headquarters location for another entity.
-
C.
hasMilitaryBase
chosen
Indicates that one entity possesses, hosts, or contains a military base associated with or located on another entity.
-
D.
garrisonIncluded
Indicates that a particular garrison is included within, or forms part of, a specified larger military force, unit, or installation.
-
E.
garrisonTown
Indicates that a town serves as a military base or station where armed forces are permanently or regularly housed.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:26 a.m.