Triple
T9962802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papyrus 66 |
E195608
|
entity |
| Predicate | hasNominaSacra |
P85107
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Papyrus 66, hasNominaSacra, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNominaSacra Context triple: [Papyrus 66, hasNominaSacra, yes]
-
A.
nominaSacra
chosen
Indicates that a word or name is written in its abbreviated sacred form, as used in early Christian manuscripts.
-
B.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
-
C.
sacredStatus
Indicates that something holds a revered, holy, or religiously significant status within a particular belief system or tradition.
-
D.
consecratedBy
Indicates that one entity has been formally made sacred, dedicated, or set apart for religious use through a ritual or act performed by another entity.
-
E.
principalSacrament
Indicates that one sacrament holds primary or highest importance in relation to another or within a given religious or ritual context.
- 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_69ca82ebd1288190912f9e4482d1fa35 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb718cd588190a4aac48220deddec |
completed | April 2, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:47 p.m.