Triple
T37829257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Broadsword |
E943150
|
entity |
| Predicate | roleInBattleOfSanCarlos |
P203981
|
FINISHED |
| Object | air-defence escort |
—
|
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: air-defence escort | Statement: [HMS Broadsword, roleInBattleOfSanCarlos, air-defence escort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBattleOfSanCarlos Context triple: [HMS Broadsword, roleInBattleOfSanCarlos, air-defence escort]
-
A.
roleInBattleOfCúcuta
Indicates the specific role or function an entity had in the Battle of Cúcuta.
-
B.
roleInMexicanWarOfIndependence
Indicates the specific part or function an entity played in the events or efforts of the Mexican War of Independence.
-
C.
roleInAraucoWar
Indicates the specific function, position, or involvement an entity had within the context of the Arauco War.
-
D.
roleInMexicanAmericanWar
Indicates that an entity participated in the Mexican–American War in a specified capacity or function.
-
E.
roleInSpanishAmericanWar
Indicates the specific function, position, or involvement an entity had in the events or activities of the Spanish–American War.
- 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0303622ce08190b359c9d247268729 |
completed | May 12, 2026, 10:39 a.m. |
| PD | Predicate disambiguation | batch_6a03030c02fc81908e546dba291b1240 |
completed | May 12, 2026, 10:38 a.m. |
| PDg | Predicate description generation | batch_6a03036152e4819082881a9f59919e1b |
completed | May 12, 2026, 10:39 a.m. |
Created at: May 3, 2026, 4:19 p.m.