Triple
T34545322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of Argeș County |
E886908
|
entity |
| Predicate | isHeraldicBanner |
P179298
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Flag of Argeș County, isHeraldicBanner, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHeraldicBanner Context triple: [Flag of Argeș County, isHeraldicBanner, true]
-
A.
hasInescutcheon
Indicates that one heraldic shield or coat of arms bears another smaller shield (an inescutcheon) placed upon it.
-
B.
heraldicStatus
Indicates the formal standing or classification of an entity within a heraldic system, such as its rank, legitimacy, or official recognition in heraldry.
-
C.
coatOfArms
Indicates that one entity serves as the heraldic emblem or coat of arms representing another entity.
-
D.
hasHeraldicOrdinary
Indicates that an entity bears or includes a specific heraldic ordinary (a basic geometric figure) as part of its coat of arms or heraldic design.
-
E.
hasHeraldicUse
Indicates that something is used as, or incorporated into, a heraldic device, emblem, or coat of arms.
- 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7201fc32c8190a79a85a7a4f63662 |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: May 1, 2026, 2:02 a.m.