Triple
T12690897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patti Lateranensi |
E303200
|
entity |
| Predicate | dataDiFirma |
P106360
|
FINISHED |
| Object | 1929-02-11 |
—
|
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: 1929-02-11 | Statement: [Patti Lateranensi, dataDiFirma, 1929-02-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataDiFirma Context triple: [Patti Lateranensi, dataDiFirma, 1929-02-11]
-
A.
documentSignedBy
Indicates that a document has been formally signed or authorized by a specific entity.
-
B.
signText
Indicates that a sign bears or displays a particular textual content.
-
C.
signatureVehicle
Indicates that the vehicle is the primary or characteristic mode of transportation associated with a particular entity (such as a person, group, or brand).
-
D.
hasSignFor
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about another entity.
-
E.
signatureItem
Indicates that an entity is a component or element that forms part of another entity’s signature (such as a defining list, pattern, or parameter set).
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d962a32c6481908ddaddae4ea267bf |
completed | April 10, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69d960be63f081908a5ef5ef17a311bf |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d96297b81c819081ad1432dc5f15f4 |
completed | April 10, 2026, 8:50 p.m. |
Created at: April 9, 2026, 5:22 p.m.