Triple
T31639398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | capture of Spanish frigate Gamo |
E807403
|
entity |
| Predicate | flagOfSpanishSide |
P73103
|
FINISHED |
| Object | Spanish Navy ensign |
E723982
|
NE 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: Spanish Navy ensign | Statement: [capture of Spanish frigate Gamo, flagOfSpanishSide, Spanish Navy ensign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flagOfSpanishSide Context triple: [capture of Spanish frigate Gamo, flagOfSpanishSide, Spanish Navy ensign]
-
A.
isWarEnsignOf
Indicates that one entity is the war ensign (a specific military or wartime flag) representing or belonging to another entity.
-
B.
nationalFlag
Indicates that one entity is the official national flag representing the other entity (a country or nation).
-
C.
historicalFlagOf
Indicates that one entity served as a former or past official flag representing another entity during a specific historical period.
-
D.
flagFlown
Indicates that a particular flag is being displayed or flown at a specific location or by a specific entity.
-
E.
flagOrInsignia
chosen
Indicates that one entity serves as a flag, emblem, or insignia representing another entity.
- F. None of above.
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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b79daba188190b3666e4e4f1d2fb5 |
completed | June 12, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:48 p.m.