Triple
T3283227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Macedonian War |
E68920
|
entity |
| Predicate | aimOfRome |
P47691
|
FINISHED |
| Object | contain Macedonian expansion |
—
|
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: contain Macedonian expansion | Statement: [First Macedonian War, aimOfRome, contain Macedonian expansion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimOfRome Context triple: [First Macedonian War, aimOfRome, contain Macedonian expansion]
-
A.
roleInRome
Indicates that an entity holds or held a specific role, position, or function within the context of Rome or Roman society.
-
B.
RomanRepresentative
Indicates that one entity serves as an official representative or agent of the Roman state, authority, or interests in relation to another entity.
-
C.
historicalEmpireCenter
Indicates that a location served as the primary political or administrative center of a historical empire.
-
D.
viewedRomanRuleAs
Indicates that one entity regarded or interpreted Roman rule in a particular way or from a particular perspective.
-
E.
ancientStates
Indicates that the related entity functioned as a state or political entity in ancient times.
- F. None of above. chosen
Provenance (4 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_69ad859c463481909ca4be267336c290 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb03621608190a2b7a6b38d6559da |
completed | March 8, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69ada421fadc8190b7c7d3c8afd20061 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada526764881908e4bd52938d5374d |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:10 p.m.