Triple
T4563280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3rd Dynasty of Egypt |
E121847
|
entity |
| Predicate | followedByPeriod |
P57700
|
FINISHED |
| Object | high Old Kingdom pyramid age |
—
|
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: high Old Kingdom pyramid age | Statement: [3rd Dynasty of Egypt, followedByPeriod, high Old Kingdom pyramid age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedByPeriod Context triple: [3rd Dynasty of Egypt, followedByPeriod, high Old Kingdom pyramid age]
-
A.
followedByClass
Indicates that one class or type is immediately succeeded by another class or type in a defined sequence or ordering.
-
B.
followedByTitle
Indicates that one title directly succeeds another in a sequence or ordered list.
-
C.
mayBeFollowedBy
Indicates that one event, state, or item is allowed or able to occur immediately after another in a sequence.
-
D.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
-
E.
followedByComponent
Indicates that one component directly succeeds another component in a defined sequence or order.
- 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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd5830b4308190a63699bf28922375 |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56f6e75481909c487a94a2c2d0ba |
completed | March 20, 2026, 2:17 p.m. |
Created at: March 20, 2026, 1:09 p.m.