Triple
T3497884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonaparte |
E73894
|
entity |
| Predicate | dynasticMotto |
P20052
|
FINISHED |
| Object | “Pour l’Empire” (associated with Napoleonic rule) |
—
|
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: “Pour l’Empire” (associated with Napoleonic rule) | Statement: [Bonaparte, dynasticMotto, “Pour l’Empire” (associated with Napoleonic rule)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynasticMotto Context triple: [Bonaparte, dynasticMotto, “Pour l’Empire” (associated with Napoleonic rule)]
-
A.
isMottoOf
chosen
Indicates that a phrase or expression serves as the official motto associated with a particular entity.
-
B.
dynasticNameDerivedFrom
Indicates that a dynastic name is derived from, or based on, another name, title, or source.
-
C.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
-
D.
dynasticOrigin
Indicates the historical dynasty or ruling family from which an entity originates or descends.
-
E.
dynasticStatus
Indicates the relationship between an entity and a ruling dynasty, such as membership in, association with, or status within that dynastic line.
- 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_69ad85cdb6e48190a335d412b9194ed8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbd299ec8190b76b165b2fd70537 |
completed | March 8, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69adae0b34908190b2bb5766a2231f7a |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.