Triple
T17071473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lion of Saint Mark |
E414230
|
entity |
| Predicate | inscriptionOftenShows |
P1726
|
FINISHED |
| Object | "Pax tibi Marce evangelista meus" |
—
|
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: "Pax tibi Marce evangelista meus" | Statement: [Lion of Saint Mark, inscriptionOftenShows, "Pax tibi Marce evangelista meus"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscriptionOftenShows Context triple: [Lion of Saint Mark, inscriptionOftenShows, "Pax tibi Marce evangelista meus"]
-
A.
inscriptionPresence
Indicates that an inscription exists or is present on, within, or associated with a given entity.
-
B.
inscriptionBy
Indicates that an inscription was created, written, or carved by a particular agent or entity.
-
C.
inscriptionSession
Indicates a relationship where an inscription is created, recorded, or associated within a particular session or event of inscribing.
-
D.
inscriptionStatus
Indicates the current state or condition of an inscription, such as whether it has been created, verified, updated, or removed.
-
E.
inscription
chosen
Indicates that text has been written, carved, or engraved onto a surface or object.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc1b7d48190979a848b4188cb22 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.