Triple
T31325222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persian conquest of Phocaea |
E798863
|
entity |
| Predicate | conqueredEntity |
P164235
|
FINISHED |
| Object | Phocaea |
—
|
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: Phocaea | Statement: [Persian conquest of Phocaea, conqueredEntity, Phocaea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conqueredEntity Context triple: [Persian conquest of Phocaea, conqueredEntity, Phocaea]
-
A.
conqueredIn
Indicates that one entity gained control over another entity or territory as a result of a specific conquest event or campaign.
-
B.
conqueredFrom
Indicates that one entity gained control of another entity by taking it from a third party that previously held it.
-
C.
conqueredState
Indicates that one state has been defeated and brought under the control or domination of another state.
-
D.
realmConqueredBy
chosen
Indicates that a particular realm or territory has been taken over and brought under the control of a specified conqueror.
-
E.
conqueredCity
Indicates that one entity has taken control of a city from another entity, typically through military force or domination.
- 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_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:15 p.m.