Triple
T34539238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Itjtawy area (probable) |
E886757
|
entity |
| Predicate | temporalStart |
P48368
|
FINISHED |
| Object | early 12th Dynasty (approximate, probable) |
—
|
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 12th Dynasty (approximate, probable) | Statement: [Itjtawy area (probable), temporalStart, early 12th Dynasty (approximate, probable)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporalStart Context triple: [Itjtawy area (probable), temporalStart, early 12th Dynasty (approximate, probable)]
-
A.
hasTemporalEnd
Indicates that an event, state, or process concludes or terminates at a specific point or interval in time.
-
B.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
C.
startDate
Indicates the point in time when an event, state, or relationship begins.
-
D.
startTimeDepicted
Indicates that the subject visually represents the starting time of an event, process, or state.
-
E.
timeStartApprox
chosen
Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 2:02 a.m.