Triple
T9962791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papyrus 66 |
E195608
|
entity |
| Predicate | paleographicalDatingMethod |
P91687
|
FINISHED |
| Object | paleography |
—
|
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: paleography | Statement: [Papyrus 66, paleographicalDatingMethod, paleography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paleographicalDatingMethod Context triple: [Papyrus 66, paleographicalDatingMethod, paleography]
-
A.
deciphermentDate
Indicates the date on which something (such as a text, code, or inscription) was successfully deciphered or decoded.
-
B.
deciphermentPeriod
Indicates the time span during which the decipherment of something (such as a script, code, or text) took place.
-
C.
chronologyCertainty
Indicates the degree of confidence or uncertainty about the ordering or dating of events or temporal relationships.
-
D.
geochronologyMethod
Indicates the method or technique used to determine the age or chronological sequence of geological materials or events.
-
E.
historicalMethod
Indicates that a particular method, approach, or technique was used in the past, typically in a historical context or during a previous period of activity.
- 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_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. |
| PDg | Predicate description generation | batch_69cd36f112bc81908b473787e702de2f |
completed | April 1, 2026, 3:17 p.m. |
Created at: March 30, 2026, 8:47 p.m.