Triple
T11780966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Audley family |
E280143
|
entity |
| Predicate | heraldicMetal |
P100889
|
FINISHED |
| Object | or |
—
|
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: or | Statement: [Audley family, heraldicMetal, or]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heraldicMetal Context triple: [Audley family, heraldicMetal, or]
-
A.
coatOfArmsMetal
chosen
Indicates that a coat of arms features a specific metal (such as gold or silver) as one of its heraldic tinctures.
-
B.
heraldicName
Indicates the formal name or designation assigned to a heraldic element (such as a coat of arms, charge, or symbol) within a heraldic system.
-
C.
heraldicTradition
Indicates a relationship where something belongs to, follows, or is characterized by a particular system or style of heraldic customs and practices.
-
D.
heralds
Indicates that one event, action, or entity serves as a sign or forerunner announcing the imminent arrival or occurrence of another.
-
E.
heraldicConnection
Indicates a relationship where entities are linked through heraldry, such as by shared coats of arms, heraldic symbols, lineage, or official armorial associations.
- 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_69d6ab01d2688190ad8ed6bda487eaa5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a8c2e8b08190a31b1e284fca2aee |
completed | April 10, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69d8a242cd8c819086ed6c5f292dc8cb |
completed | April 10, 2026, 7:09 a.m. |
Created at: April 8, 2026, 9:42 p.m.