Triple
T17461499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artaxerxes IV Arses |
E425159
|
entity |
| Predicate | notableEventDuringLifetime |
P53982
|
FINISHED |
| Object | Macedonian expansion under Philip II |
—
|
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: Macedonian expansion under Philip II | Statement: [Artaxerxes IV Arses, notableEventDuringLifetime, Macedonian expansion under Philip II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEventDuringLifetime Context triple: [Artaxerxes IV Arses, notableEventDuringLifetime, Macedonian expansion under Philip II]
-
A.
notableEventInLife
chosen
Indicates that a particular event holds significant importance or impact within an entity’s life or personal history.
-
B.
notableEventMentionedIn
Indicates that a particular notable event is referenced or discussed within a specified source or document.
-
C.
hasNamesakeNotableEvent
Indicates that one entity serves as the namesake for a notable event associated with the other entity.
-
D.
famousForEvent
Indicates that an entity is widely known or recognized specifically because of a particular event.
-
E.
notableEventDate
Indicates the date on which a notable or significant event associated with the subject 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451a3c4cc8190937808e3272272c0 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.