Triple
T31325221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persian conquest of Phocaea |
E798863
|
entity |
| Predicate | conqueror |
P164235
|
FINISHED |
| Object | Achaemenid Persian 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 Persian Empire | Statement: [Persian conquest of Phocaea, conqueror, Achaemenid Persian Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conqueror Context triple: [Persian conquest of Phocaea, conqueror, Achaemenid Persian Empire]
-
A.
conqueredByRuler
Indicates that a place, people, or entity was taken over and brought under control through force or domination by a specific ruler.
-
B.
encounteredConqueror
Indicates that one entity has come into contact with or faced a conquering entity, typically in a context of conflict, dominance, or subjugation.
-
C.
realmConqueredBy
chosen
Indicates that a particular realm or territory has been taken over and brought under the control of a specified conqueror.
-
D.
besieger
Indicates that one entity is laying siege to, or conducting a siege against, another entity.
-
E.
conqueredFrom
Indicates that one entity gained control of another entity by taking it from a third party that previously held it.
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69eb008808190bdf42de72d202baf |
completed | May 3, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:15 p.m.