Triple
T537261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puerto Rican coat of arms |
E12352
|
entity |
| Predicate | oneOfOldestCoatsOfArmsInAmericas |
P16593
|
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: [Puerto Rican coat of arms, oneOfOldestCoatsOfArmsInAmericas, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oneOfOldestCoatsOfArmsInAmericas Context triple: [Puerto Rican coat of arms, oneOfOldestCoatsOfArmsInAmericas, true]
-
A.
coatOfArms
Indicates that one entity serves as the heraldic emblem or coat of arms representing another entity.
-
B.
coatOfArmsMotto
Indicates the phrase or motto that appears on or is officially associated with a particular coat of arms.
-
C.
nationalFlag
Indicates that one entity is the official national flag representing the other entity (a country or nation).
-
D.
hasColonialHistoryWith
Indicates that one entity has a historical relationship of colonization or being colonized involving the other entity.
-
E.
heraldicTradition
Indicates a relationship where something belongs to, follows, or is characterized by a particular system or style of heraldic customs and practices.
- 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b51ff08190a39f4168fd9a7ddf |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a49857e1148190aa782b82675cf0b5 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.