Triple
T23881810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lygon family |
E600221
|
entity |
| Predicate | heraldicMotto |
P10484
|
FINISHED |
| Object | “Le bon temps viendra” |
—
|
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: “Le bon temps viendra” | Statement: [Lygon family, heraldicMotto, “Le bon temps viendra”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heraldicMotto Context triple: [Lygon family, heraldicMotto, “Le bon temps viendra”]
-
A.
coatOfArmsMotto
chosen
Indicates the phrase or motto that appears on or is officially associated with a particular coat of arms.
-
B.
mottoOrInsigniaTheme
Indicates that a motto or insignia is based on, refers to, or thematically centers around a particular concept, idea, or subject.
-
C.
honorificMotto
Indicates that one entity serves as an honorific motto or formal laudatory phrase associated with another entity.
-
D.
isTraditionalMottoOf
Indicates that a phrase or saying serves as the historically established or customary motto associated with a particular entity.
-
E.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
- 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_69e295318e148190b9979d8fc02e168f |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cc05e4d48190864fc47bdffa4ca9 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:24 p.m.