Triple
T18109923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mazaces |
E433445
|
entity |
| Predicate | endCauseOfRule |
P54944
|
FINISHED |
| Object | Macedonian conquest |
—
|
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 conquest | Statement: [Mazaces, endCauseOfRule, Macedonian conquest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endCauseOfRule Context triple: [Mazaces, endCauseOfRule, Macedonian conquest]
-
A.
reasonForEndOfRule
chosen
Indicates the cause, circumstance, or event that led to the termination or conclusion of a particular rule or period of rule.
-
B.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
C.
end cause
Indicates that one event or action brings about the termination or cessation of another event, state, or process.
-
D.
eligibleCause
Indicates that one entity qualifies as a valid or acceptable cause or reason for another entity or outcome.
-
E.
causeStatus
Indicates that one entity brings about, initiates, or is responsible for a particular state or condition in another entity.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd13cb48190bff06b472e34dd0e |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.