Triple
T10326954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senusret I |
E242783
|
entity |
| Predicate | coregencyDurationApprox |
P93385
|
FINISHED |
| Object | about 10 years |
—
|
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: about 10 years | Statement: [Senusret I, coregencyDurationApprox, about 10 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coregencyDurationApprox Context triple: [Senusret I, coregencyDurationApprox, about 10 years]
-
A.
eraDuration
Indicates the length of time that a particular era or period spans.
-
B.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
C.
banDurationApproximate
Indicates that the duration of a ban is known only approximately rather than as an exact, precise time period.
-
D.
typicalRecordingDuration
Indicates the usual or standard length of time that something is recorded.
-
E.
possibleDuration
Indicates the range or specific length of time that an action, event, or state can last or is allowed to last.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ce69b881909f27d97c90643634 |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d7cada7881908beba55a1dc9ecb9 |
completed | April 7, 2026, 10:09 a.m. |
Created at: April 6, 2026, 11:51 a.m.