Triple
T31148355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Hardy |
E793994
|
entity |
| Predicate | flotillaLeaderOf |
P70436
|
FINISHED |
| Object | 2nd Destroyer Flotilla |
—
|
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: 2nd Destroyer Flotilla | Statement: [HMS Hardy, flotillaLeaderOf, 2nd Destroyer Flotilla]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flotillaLeaderOf Context triple: [HMS Hardy, flotillaLeaderOf, 2nd Destroyer Flotilla]
-
A.
squadronFlagshipOf
chosen
Indicates that one entity serves as the primary or lead flagship vessel of a particular squadron.
-
B.
roleInFirstFleet
Indicates that an entity held a specific role or position within the First Fleet.
-
C.
fleetFlagshipOf
Indicates that one entity serves as the primary or leading flagship of a particular fleet.
-
D.
captainServedUnder
Indicates that one captain performed their service or held their position under the authority or command of another person.
-
E.
navalRankFlagshipOf
Indicates that a naval rank is associated with, or designated as, the flagship command of, a particular vessel or fleet.
- 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_69f224d41bb48190a5621cd1485e3a30 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:06 p.m.