Triple
T1038764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Henry |
E22422
|
entity |
| Predicate | builtToDefend |
P8412
|
FINISHED |
| Object | entrance to Rideau Canal |
—
|
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: entrance to Rideau Canal | Statement: [Fort Henry, builtToDefend, entrance to Rideau Canal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtToDefend Context triple: [Fort Henry, builtToDefend, entrance to Rideau Canal]
-
A.
defensiveStructure
chosen
Indicates a relationship where one entity functions as a structure built or used to protect, defend, or fortify another entity or area.
-
B.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
C.
defender
Indicates a relationship where one entity protects, guards, or supports another entity against threats, attacks, or criticism.
-
D.
builtForConflict
Indicates that something is specifically designed or intended to function effectively in situations of conflict or confrontation.
-
E.
defenseResult
Indicates the outcome or consequence of a defensive action or strategy in response to an attack or threat.
- 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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b97c64a88190bf1119fdd4940bf3 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b729f8488190b2042bd9c625a833 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.