Triple
T8794815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | flag of Haarlemmermeer |
E209262
|
entity |
| Predicate | countryFlagType |
P85427
|
FINISHED |
| Object | subnational flag |
—
|
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: subnational flag | Statement: [flag of Haarlemmermeer, countryFlagType, subnational flag]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryFlagType Context triple: [flag of Haarlemmermeer, countryFlagType, subnational flag]
-
A.
flagCode
Indicates the specific flag identifier or code associated with an entity, typically representing its national, regional, or organizational affiliation.
-
B.
nationalFlag
Indicates that one entity is the official national flag representing the other entity (a country or nation).
-
C.
adoptedAsRegionalFlagInCountry
Indicates that a flag has been officially adopted for use as a regional flag within a specific country.
-
D.
subnationalFlagOf
Indicates that one flag represents or is officially used by a subnational entity (such as a state, province, or region) within a larger sovereign country.
-
E.
symbolCountry
Indicates that a symbol (such as a flag, emblem, or icon) is associated with or represents a specific country.
- 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_69ca836240888190a62b262e56a69d2f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fa0c6008190a5c4d87510ad5bbd |
completed | March 31, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1d48f08190b325a77d4c76d223 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cfddef48190aee764ee7b25bae9 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:43 p.m.