Triple
T1286075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cippus Perusinus |
E27435
|
entity |
| Predicate | inscriptionCompleteness |
P26754
|
FINISHED |
| Object | partially preserved |
—
|
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: partially preserved | Statement: [Cippus Perusinus, inscriptionCompleteness, partially preserved]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscriptionCompleteness Context triple: [Cippus Perusinus, inscriptionCompleteness, partially preserved]
-
A.
inscriptionBy
Indicates that an inscription was created, written, or carved by a particular agent or entity.
-
B.
inscription
Indicates that text has been written, carved, or engraved onto a surface or object.
-
C.
inscriptionLocation
Indicates the place or surface on which an inscription is written or engraved.
-
D.
inscriptionType
Indicates the specific kind or category of inscription associated with an entity (e.g., dedicatory, funerary, commemorative).
-
E.
mandatesInscription
Indicates that one entity requires or orders that an inscription be made on or associated with another entity.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0b85eb48190a8b61dc397fa6390 |
completed | March 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69a4bee276d8819092f71c5a1140bb61 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bf60545c8190901ccfb2cb7c4b41 |
completed | March 1, 2026, 10:36 p.m. |
Created at: March 1, 2026, 7:51 p.m.