Triple
T33409453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seth Meribre |
E855534
|
entity |
| Predicate | periodPosition |
P10549
|
FINISHED |
| Object | later Thirteenth Dynasty (approximate) |
—
|
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: later Thirteenth Dynasty (approximate) | Statement: [Seth Meribre, periodPosition, later Thirteenth Dynasty (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodPosition Context triple: [Seth Meribre, periodPosition, later Thirteenth Dynasty (approximate)]
-
A.
periodProperty
Indicates a temporal characteristic or attribute associated with a specific time period or interval.
-
B.
periodizedAs
Indicates that something has been divided or organized into distinct time periods according to a particular periodization scheme.
-
C.
positionInMonth
Indicates the specific ordinal position or occurrence of something within a given month (e.g., first, second, third).
-
D.
positionInEra
chosen
Indicates the temporal placement or role of something within a specific historical or chronological era.
-
E.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:36 a.m.