Triple
T2807423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commodore Henry Harwood’s Force G |
E54085
|
entity |
| Predicate | shipTypeInForce |
P19503
|
FINISHED |
| Object | light cruiser |
—
|
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: light cruiser | Statement: [Commodore Henry Harwood’s Force G, shipTypeInForce, light cruiser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipTypeInForce Context triple: [Commodore Henry Harwood’s Force G, shipTypeInForce, light cruiser]
-
A.
fleetType
Indicates the category or classification of a fleet to which an entity belongs or with which it is associated.
-
B.
shipClass
Indicates the classification or type category to which a particular ship belongs.
-
C.
navalForceComposition
chosen
Indicates the makeup and distribution of different types of naval units or vessels within a particular naval force.
-
D.
navalStandardType
Indicates the specific naval standard or classification system under which an entity (such as a vessel, equipment, or procedure) is defined or regulated.
-
E.
navalFleet
Indicates a relationship where multiple naval vessels are organized and operate together as a coordinated maritime military force.
- 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_69ab49dcee188190b5c6eca9ae9e3469 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde2ec2ac8190bd702ad3eafb6aed |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd059f308190853191f6ffe2bc6f |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.