Triple
T33752407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Glatton |
E864879
|
entity |
| Predicate | BlighCommandStart |
P177274
|
FINISHED |
| Object | 1795 |
—
|
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: 1795 | Statement: [HMS Glatton, BlighCommandStart, 1795]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BlighCommandStart Context triple: [HMS Glatton, BlighCommandStart, 1795]
-
A.
commandedFromShip
Indicates that an entity exercised command or control over something while located on or operating from a ship.
-
B.
commandedTo
Indicates that one entity has issued an order or directive for another entity to perform a specific action or fulfill a particular duty.
-
C.
commandeeredBy
Indicates that control or possession of something has been forcibly taken over by a particular agent or group.
-
D.
commandingOfficerAtManilaBay
Indicates that one entity served as the commanding officer at the Battle of Manila Bay.
-
E.
commanderOfAttackedShip
Indicates that one entity is the commanding officer of a ship that is the target of an attack.
- F. None of above. chosen
Provenance (4 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb9142a881908bd4784689cce14a |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f96ea0c08190902a3d0e1f263e8c |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fa335b908190a20d92d5396203b5 |
completed | May 3, 2026, 7:33 a.m. |
Created at: May 1, 2026, 1:45 a.m.