Triple
T4345639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Visconti serpent |
E97892
|
entity |
| Predicate | hasMottoContext |
P56183
|
FINISHED |
| Object | Visconti family mottos and devices |
—
|
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: Visconti family mottos and devices | Statement: [Visconti serpent, hasMottoContext, Visconti family mottos and devices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMottoContext Context triple: [Visconti serpent, hasMottoContext, Visconti family mottos and devices]
-
A.
hasMottoInText
Indicates that an entity has a motto expressed in a specific textual form or wording.
-
B.
hasMottoLikeFunction
Indicates that something serves a role or function similar to a motto, typically expressing a guiding principle, slogan, or core message.
-
C.
usesMotto
Indicates that one entity adopts or employs a particular motto as its guiding phrase or slogan.
-
D.
hasMottoOrigin
Indicates that a motto originates from, or is derived from, a particular source, place, or context.
-
E.
hasMottoTradition
Indicates that an entity possesses a traditional motto associated with its identity or heritage.
- F. None of above. chosen
Provenance (4 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_69b34548402c819085ab68b27c235a87 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3518bec408190ba07643bbf7eb632 |
completed | March 12, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69b34f4fe1c481908d6d66e15697c04b |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b350d1649881908fa6556d875a8b4d |
completed | March 12, 2026, 11:48 p.m. |
Created at: March 12, 2026, 11:15 p.m.