Triple
T37867760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of Aargau |
E944520
|
entity |
| Predicate | hasDesignInCommonWith |
P69276
|
FINISHED |
| Object | coat of arms of Aargau |
—
|
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: coat of arms of Aargau | Statement: [Flag of Aargau, hasDesignInCommonWith, coat of arms of Aargau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDesignInCommonWith Context triple: [Flag of Aargau, hasDesignInCommonWith, coat of arms of Aargau]
-
A.
wearsSameDesignAs
Indicates that two entities are wearing items that share the same design or pattern.
-
B.
sharesDesignFeaturesWith
chosen
Indicates that two entities have similar or overlapping design characteristics, structures, or stylistic elements.
-
C.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
D.
hasDifferentDesignsFor
Indicates that one entity provides or uses multiple distinct designs tailored for different other entities or contexts.
-
E.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffb97b8ff8819088b105d99a0820c9 |
completed | May 9, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69ffb88ef7388190a710120ed76edc0e |
completed | May 9, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:19 p.m.