Triple
T25597078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Nectanebo |
E641683
|
entity |
| Predicate | endedWithConquestBy |
P32947
|
FINISHED |
| Object | Achaemenid Empire |
—
|
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: Achaemenid Empire | Statement: [House of Nectanebo, endedWithConquestBy, Achaemenid Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endedWithConquestBy Context triple: [House of Nectanebo, endedWithConquestBy, Achaemenid Empire]
-
A.
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.
-
B.
afterConquest
Indicates that one event, state, or condition occurs subsequent to and as a result of a conquest having taken place.
-
C.
conquestPeriod
Indicates the time span during which one entity successfully subjugates or takes control of another through conquest.
-
D.
conqueredIn
chosen
Indicates that one entity gained control over another entity or territory as a result of a specific conquest event or campaign.
-
E.
afterConquestName
Indicates that an entity’s name is the one it is known by after a conquest or successful takeover has occurred.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9a30ad081909c4acab2736475a1 |
completed | May 2, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 4:28 p.m.