Triple
T20090152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxyrhynchus Papyri |
E496246
|
entity |
| Predicate | latestDocumentsDate |
P20103
|
FINISHED |
| Object | early Islamic period |
—
|
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: early Islamic period | Statement: [Oxyrhynchus Papyri, latestDocumentsDate, early Islamic period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: latestDocumentsDate Context triple: [Oxyrhynchus Papyri, latestDocumentsDate, early Islamic period]
-
A.
latestManuscriptsDateTo
chosen
Indicates the most recent date up to which the manuscripts in question are known, valid, or considered.
-
B.
lastEntryDate
Indicates the date on which the most recent entry, record, or update associated with the subject occurred.
-
C.
latestPossibleDate
Indicates the most recent date on which a given event, condition, or state can validly or feasibly occur.
-
D.
latestEntriesDateFrom
Indicates the starting date from which the most recent entries in a set or system are considered or retrieved.
-
E.
retrievalDate
Indicates the date on which an item, record, or resource was accessed, obtained, or retrieved.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6655e1ef0819095f40a1ce2eb17b7 |
completed | April 20, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:20 p.m.