Triple
T1776190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of New Jersey |
E38984
|
entity |
| Predicate | coatOfArmsShieldCharge |
P2907
|
FINISHED |
| Object | three plows |
—
|
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: three plows | Statement: [Flag of New Jersey, coatOfArmsShieldCharge, three plows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coatOfArmsShieldCharge Context triple: [Flag of New Jersey, coatOfArmsShieldCharge, three plows]
-
A.
coatOfArms
Indicates that one entity serves as the heraldic emblem or coat of arms representing another entity.
-
B.
coatOfArmsFeatures
chosen
Indicates that a coat of arms includes or displays specific symbols, colors, or design elements as part of its heraldic composition.
-
C.
coatOfArmsMotto
Indicates the phrase or motto that appears on or is officially associated with a particular coat of arms.
-
D.
coatOfArmsPosition
Indicates the spatial placement or arrangement of a coat of arms relative to another object, surface, or reference frame.
-
E.
usesCoatOfArmsVariant
Indicates that an entity employs an alternative or modified version of a standard coat of arms rather than the primary or original design.
- 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_69a8862e61708190af97b9838cc3f5de |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab74dc9d1481908084ef07872a71f8 |
completed | March 7, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69aa61cf3ca881908641fd73ce2f7c9d |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.