Triple
T21298111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Strafford |
E524980
|
entity |
| Predicate | garrisonOrCrewType |
P143638
|
FINISHED |
| Object | Royal Navy sailors |
—
|
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: Royal Navy sailors | Statement: [HMS Strafford, garrisonOrCrewType, Royal Navy sailors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonOrCrewType Context triple: [HMS Strafford, garrisonOrCrewType, Royal Navy sailors]
-
A.
garrisonType
Indicates the specific kind or classification of military garrison associated with an entity.
-
B.
garrisonForceType
Indicates the specific type or classification of military force assigned to occupy, defend, or maintain control of a particular location.
-
C.
garrisonOrMobility
Indicates a relationship where an entity either serves as a stationary defensive presence (garrison) or provides movement/transport capability (mobility) for another entity or location.
-
D.
garrisonSize
Indicates the number of troops or defenders stationed at a particular location as its garrison.
-
E.
garrisonSide
Indicates the side, faction, or allegiance that a garrison is associated with or belongs to.
- 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_69e0b517e6748190850d6f6ddf323d69 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7385a24d08190bfd410c7f10fa6f7 |
completed | April 21, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 4:04 p.m.