Triple
T125165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of Bermuda |
E2530
|
entity |
| Predicate | designOrigin |
P1823
|
FINISHED |
| Object | British maritime ensign tradition |
—
|
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: British maritime ensign tradition | Statement: [Flag of Bermuda, designOrigin, British maritime ensign tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designOrigin Context triple: [Flag of Bermuda, designOrigin, British maritime ensign tradition]
-
A.
designedIn
Indicates that something was created, planned, or conceived during a particular time period or at a specific location.
-
B.
designedBy
Indicates that one entity is the creator, planner, or architect responsible for the form or structure of another entity.
-
C.
countryOfOrigin
Indicates the country from which an entity originally comes or was first produced, created, or established.
-
D.
placeOfOrigin
Indicates the location or source from which an entity originally comes or was created.
-
E.
historicalOrigin
chosen
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
- 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_69a251b54ea88190b18281669f59b4c0 |
completed | Feb. 28, 2026, 2:23 a.m. |
| NER | Named-entity recognition | batch_69a2573e4e6481908252dfef2e34f46e |
completed | Feb. 28, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69a2564a54948190ba30bee858173b27 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:27 a.m.