Triple
T25140439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republic of Haiti (southern state) |
E629786
|
entity |
| Predicate | flagBelongsTo |
P73103
|
FINISHED |
| Object | Haiti (historical flags) |
—
|
NE NERFINISHED |
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: Haiti (historical flags) | Statement: [Republic of Haiti (southern state), flagBelongsTo, Haiti (historical flags)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flagBelongsTo Context triple: [Republic of Haiti (southern state), flagBelongsTo, Haiti (historical flags)]
-
A.
flagOrigin
Indicates the place or source from which a flag originates or is derived.
-
B.
flagFamily
Indicates that one flag is part of, or associated with, a broader family or group of related flags.
-
C.
flagElement
Indicates that one entity serves as a flag or marker element associated with another entity, typically used to signal a condition, state, or special handling.
-
D.
flag
Indicates that one entity marks, signals, or draws attention to another entity, often to denote status, importance, or the need for review or action.
-
E.
flagOrInsignia
chosen
Indicates that one entity serves as a flag, emblem, or insignia representing 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f468475218819089b73a0d2e072110 |
completed | May 1, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:29 a.m.