Triple
T4729835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Pavia (1525) |
E104977
|
entity |
| Predicate | mottoOrQuote |
P42
|
FINISHED |
| Object | Francis I’s reported message: “All is lost save honor.” |
—
|
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: Francis I’s reported message: “All is lost save honor.” | Statement: [Battle of Pavia (1525), mottoOrQuote, Francis I’s reported message: “All is lost save honor.”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mottoOrQuote Context triple: [Battle of Pavia (1525), mottoOrQuote, Francis I’s reported message: “All is lost save honor.”]
-
A.
motto
chosen
Indicates that one entity serves as the guiding phrase, slogan, or maxim associated with another entity.
-
B.
mottoType
Indicates the specific category or kind of motto that characterizes the relationship between an entity and its motto.
-
C.
mottoInscription
Indicates that a particular motto is inscribed on or associated as an inscription with an entity.
-
D.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
-
E.
mottoAuthor
Indicates that one entity is the creator or originator of the motto associated with another entity.
- 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_69bd43ed84648190ae0b7ee8e8d00482 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6220071881909670c89d072ffb6d |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:19 p.m.