Triple
T27227953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camperdown |
E682067
|
entity |
| Predicate | hasCommanderForBritishSide |
P15644
|
FINISHED |
| Object | Admiral Adam Duncan |
—
|
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: Admiral Adam Duncan | Statement: [Camperdown, hasCommanderForBritishSide, Admiral Adam Duncan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommanderForBritishSide Context triple: [Camperdown, hasCommanderForBritishSide, Admiral Adam Duncan]
-
A.
commandingOfficerBritishSide
chosen
Indicates that one entity serves as the commanding officer of another entity on the British side in a military context.
-
B.
hasCommander
Indicates that one entity serves as the commanding officer or leader of another entity.
-
C.
BritishCommanderStatus
Indicates that an entity holds, held, or is assigned the role or status of a British military commander in a given context.
-
D.
hasAlliedLeader
Indicates that one entity serves as an allied leader or commander in relation to another entity.
-
E.
notableCommanderNationality
Indicates that the notable commander associated with an entity has the specified nationality.
- 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fed83b1d188190a318b0ad3003200a |
completed | May 9, 2026, 6:46 a.m. |
| PD | Predicate disambiguation | batch_69fed78e03548190b6e6ad93ae8d131d |
completed | May 9, 2026, 6:43 a.m. |
Created at: April 27, 2026, 9:45 a.m.