Triple
T26045971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Persian Period of Egypt |
E647833
|
entity |
| Predicate | reconqueredFrom |
P5759
|
FINISHED |
| Object | Nectanebo II |
—
|
NE NERFINISHED |
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: Nectanebo II | Statement: [Second Persian Period of Egypt, reconqueredFrom, Nectanebo II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reconqueredFrom Context triple: [Second Persian Period of Egypt, reconqueredFrom, Nectanebo II]
-
A.
conqueredFrom
chosen
Indicates that one entity gained control of another entity by taking it from a third party that previously held it.
-
B.
conqueredIn
Indicates that one entity gained control over another entity or territory as a result of a specific conquest event or campaign.
-
C.
conqueredInPartBy
Indicates that one entity has gained control over a portion, but not the entirety, of another entity through conquest.
-
D.
wasRecapturedBy
Indicates that an entity which had previously escaped or been released was caught again by another entity.
-
E.
afterConquestBy
Indicates that one entity exists in a state, condition, or situation that occurs subsequent to and as a result of being conquered by another entity.
- 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_69e77e8d419481908004e6318d28aaab |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f60c698ae48190871cd445422bad91 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 22, 2026, 9:10 a.m.