Triple
T13915321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Pavia |
E334605
|
entity |
| Predicate | hasPastoralMottoType |
P504
|
FINISHED |
| Object | episcopal motto |
—
|
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: episcopal motto | Statement: [Bishop of Pavia, hasPastoralMottoType, episcopal motto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPastoralMottoType Context triple: [Bishop of Pavia, hasPastoralMottoType, episcopal motto]
-
A.
hasMottoAuthority
Indicates that an entity has the official power or right to establish, approve, or oversee the use of a motto for another entity.
-
B.
mottoPresent
Indicates that an entity currently has an official motto associated with it.
-
C.
hasMottoTradition
Indicates that an entity possesses a traditional motto associated with its identity or heritage.
-
D.
mottoType
chosen
Indicates the specific category or kind of motto that characterizes the relationship between an entity and its motto.
-
E.
usesMotto
Indicates that one entity adopts or employs a particular motto as its guiding phrase or slogan.
- 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de27260ae08190be45b4b15898e365 |
completed | April 14, 2026, 11:38 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:16 p.m.