Triple
T330264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Red Ensign |
E6609
|
entity |
| Predicate | inUseAsRoyalNavyEnsignUntil |
P11487
|
FINISHED |
| Object | 1864 |
—
|
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: 1864 | Statement: [British Red Ensign, inUseAsRoyalNavyEnsignUntil, 1864]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUseAsRoyalNavyEnsignUntil Context triple: [British Red Ensign, inUseAsRoyalNavyEnsignUntil, 1864]
-
A.
flagFlown
Indicates that a particular flag is being displayed or flown at a specific location or by a specific entity.
-
B.
strickenFromNavalRegister
Indicates that a vessel has been officially removed from a navy’s active register, ending its status as a commissioned naval ship.
-
C.
navy
Indicates that an entity serves as or is associated with a nation's naval military force.
-
D.
fleetFlagshipOf
Indicates that one entity serves as the primary or leading flagship of a particular fleet.
-
E.
featuredUnionJackVariant
Indicates that an entity prominently displays or uses a specific variant of the Union Jack as a key identifying or decorative feature.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eaaeb64881909c7ab9bca3378e2b |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94c6d8881908239d3788c018adf |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea09a5e881908b313cb37409a4f9 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.