Triple
T33547234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turin Papyrus of Kings |
E859237
|
entity |
| Predicate | periodsCovered |
P3058
|
FINISHED |
| Object | Predynastic rulers (possibly) |
—
|
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: Predynastic rulers (possibly) | Statement: [Turin Papyrus of Kings, periodsCovered, Predynastic rulers (possibly)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodsCovered Context triple: [Turin Papyrus of Kings, periodsCovered, Predynastic rulers (possibly)]
-
A.
timePeriodCoveredTo
chosen
Indicates the span or duration of time that is encompassed, addressed, or relevant to a given subject or entity.
-
B.
interestCoveragePeriod
Indicates the time span over which interest payments or interest coverage is calculated or applies.
-
C.
timeHorizonCovered
Indicates the span or duration of time that is encompassed or addressed by something (such as a plan, forecast, or agreement).
-
D.
eligibilityPeriod
Indicates the span of time during which an entity qualifies for or is allowed to receive a particular benefit, service, or status.
-
E.
policyPeriod
Indicates the time span during which a particular policy is in effect or valid.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 1:39 a.m.