Triple
T31639408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | capture of Spanish frigate Gamo |
E807403
|
entity |
| Predicate | BritishShipNation |
P98626
|
FINISHED |
| Object | United Kingdom |
—
|
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: United Kingdom | Statement: [capture of Spanish frigate Gamo, BritishShipNation, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BritishShipNation Context triple: [capture of Spanish frigate Gamo, BritishShipNation, United Kingdom]
-
A.
BritishShipRate
Indicates that the subject is classified or rated according to the British naval ship rating system (e.g., first-rate, second-rate, etc.).
-
B.
BritishShipType
Indicates that the entity is classified as a type of ship associated with Britain, typically by origin, design, or service.
-
C.
countryOfBritishShips
chosen
Indicates the country to which British ships belong or are registered.
-
D.
approximateEnglishShips
Indicates that one entity is an estimated or approximate count of English ships associated with another entity or context.
-
E.
BritishShipArmamentApproximate
Indicates that a British ship’s armament is specified in approximate rather than exact terms.
- 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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 10:48 p.m.