Triple
T18987636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spartan–Persian War |
E464596
|
entity |
| Predicate | objectiveOfPersia |
P109222
|
FINISHED |
| Object | reassertion of Persian authority in Asia Minor |
—
|
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: reassertion of Persian authority in Asia Minor | Statement: [Spartan–Persian War, objectiveOfPersia, reassertion of Persian authority in Asia Minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectiveOfPersia Context triple: [Spartan–Persian War, objectiveOfPersia, reassertion of Persian authority in Asia Minor]
-
A.
strategicObjectiveOttoman
Indicates that one entity serves as or relates to a strategic objective or goal specifically concerning the Ottoman Empire.
-
B.
primaryObjectiveOfEmpire
chosen
Indicates the main strategic goal or overarching purpose that an empire seeks to achieve or maintain.
-
C.
objectiveOfFrance
Indicates that something is an objective, goal, or aim pursued by France.
-
D.
objectiveOfIraq
Indicates that something is the goal, aim, or intended target associated with Iraq.
-
E.
objectiveOfEgypt
Indicates that something is the goal, aim, or intended outcome pursued by Egypt.
- 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6618ab881909c0ed94930e42e68 |
completed | April 20, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.