Triple
T24517629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort George, Highland, Scotland |
E606417
|
entity |
| Predicate | hasDefence |
P129572
|
FINISHED |
| Object | dry ditch and glacis |
—
|
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: dry ditch and glacis | Statement: [Fort George, Highland, Scotland, hasDefence, dry ditch and glacis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDefence Context triple: [Fort George, Highland, Scotland, hasDefence, dry ditch and glacis]
-
A.
providesDefence
chosen
Indicates that one entity offers protection or defensive support to another entity.
-
B.
hasBaseDefense
Indicates that an entity possesses a specified level or value of defensive capability in its default or starting state.
-
C.
hasDefenseStrategy
Indicates that an entity employs or is associated with a particular plan or set of measures designed to protect against threats or attacks.
-
D.
defenceUsed
Indicates that a particular defensive measure, tactic, or argument was employed in response to a threat, attack, or accusation.
-
E.
hasDefenderStrength
Indicates that an entity possesses a certain level or measure of defensive capability or protective power.
- 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.