Triple
T537268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puerto Rican coat of arms |
E12352
|
entity |
| Predicate | bannerSymbolizes |
P129
|
FINISHED |
| Object | Christian victory |
—
|
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: Christian victory | Statement: [Puerto Rican coat of arms, bannerSymbolizes, Christian victory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bannerSymbolizes Context triple: [Puerto Rican coat of arms, bannerSymbolizes, Christian victory]
-
A.
symbolizes
chosen
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
B.
protectiveEmblemName
Indicates that a given name is the designated title or label of a protective emblem associated with an entity or context.
-
C.
symbolDescription
Indicates that a symbol is associated with or defined by a particular descriptive explanation or meaning.
-
D.
recognizesProtectiveEmblem
Indicates that an entity acknowledges and respects a designated protective emblem as carrying special protected status or immunity.
-
E.
emblemFeatures
Indicates that an emblem includes or displays specific visual elements or characteristics.
- 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_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. |
Created at: March 1, 2026, 7:32 p.m.