Triple
T3988117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stele of Novilara |
E86921
|
entity |
| Predicate | interpretationStatus |
P11828
|
FINISHED |
| Object | partially undeciphered |
—
|
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 undeciphered | Statement: [Stele of Novilara, interpretationStatus, partially undeciphered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interpretationStatus Context triple: [Stele of Novilara, interpretationStatus, partially undeciphered]
-
A.
interpretiveStatus
Indicates the evaluative or explanatory stance assigned to something, such as how it is understood, classified, or interpreted within a given context.
-
B.
interpretationMethod
Indicates the method, technique, or process used to interpret or derive meaning from something.
-
C.
deciphermentStatus
chosen
Indicates the degree to which something (such as a text, code, or inscription) has been successfully decoded or interpreted.
-
D.
containsInterpretationOf
Indicates that one entity includes or embodies an interpretation or understanding of another entity.
-
E.
signInterpretation
Indicates that one entity provides or assigns a particular meaning, explanation, or reading to a given sign, symbol, or signal.
- 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_69aed93fd9d4819085d3b2137d2346cb |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb81040481909b22e4c445ecae0f |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef8f692008190bf4d637ffc3d3eaa |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.