Triple
T29846217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Fort William (1746) |
E757934
|
entity |
| Predicate | wasCommandedByDefender |
P14510
|
FINISHED |
| Object | Major William Cockburn |
—
|
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: Major William Cockburn | Statement: [Siege of Fort William (1746), wasCommandedByDefender, Major William Cockburn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasCommandedByDefender Context triple: [Siege of Fort William (1746), wasCommandedByDefender, Major William Cockburn]
-
A.
commanderForDefender
chosen
Indicates that an entity serves as the commanding officer or leader responsible for directing and overseeing a defending force or defender.
-
B.
defenderIn
Indicates that an entity serves as a defensive agent or protector within a specified context, situation, or domain.
-
C.
awardedToDefenders
Indicates that something (such as a title, honor, or recognition) is granted specifically to entities serving in a defensive role.
-
D.
commandedBySide
Indicates that an action, unit, or operation is under the authority or control of a specified side or faction.
-
E.
commandedBy
Indicates that one entity holds authoritative control or issues orders over another entity.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f676438624819086aabd1b6e5fef4c |
completed | May 2, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 5:42 p.m.