Triple
T1078359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tricolor flag of Bolivia |
E23889
|
entity |
| Predicate | usedAtSeaAs |
P4959
|
FINISHED |
| Object | civil ensign |
—
|
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: civil ensign | Statement: [tricolor flag of Bolivia, usedAtSeaAs, civil ensign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAtSeaAs Context triple: [tricolor flag of Bolivia, usedAtSeaAs, civil ensign]
-
A.
usesAtSea
chosen
Indicates that something is employed, operated, or applied in a maritime or oceanic environment.
-
B.
maritimeUsage
Indicates the extent to which something is used for or involved in maritime activities, such as sea transport, navigation, or ocean-related operations.
-
C.
shipUsed
Indicates that a particular ship was employed or utilized in carrying out an event, activity, or operation.
-
D.
usedInMaritimeNavigation
Indicates that something is employed as a tool, aid, or reference in the practice of maritime navigation.
-
E.
aboardShip
Indicates that one entity is physically on or inside a ship, typically as a passenger, crew member, or cargo.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b943b41481909b24050ca7e78971 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73ba8208190be7f3cef8c18689b |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.