Triple
T29031645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syphax |
E737741
|
entity |
| Predicate | initialForeignPolicy |
P159858
|
FINISHED |
| Object | pro-Roman |
—
|
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: pro-Roman | Statement: [Syphax, initialForeignPolicy, pro-Roman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialForeignPolicy Context triple: [Syphax, initialForeignPolicy, pro-Roman]
-
A.
foreignPolicyContext
Indicates the broader international relations setting or circumstances within which a foreign policy decision, action, or stance occurs.
-
B.
diplomaticPolicy
Indicates the stance, strategy, or set of guiding principles an entity adopts in managing its diplomatic relations and interactions with others.
-
C.
foreignPolicyCharacteristic
chosen
Indicates a defining feature or quality of an entity’s foreign policy.
-
D.
foreignPolicyProgram
Indicates a program or initiative that defines, guides, or implements a state's foreign policy toward other international actors.
-
E.
foreignPolicyArea
Indicates the specific domain or topic within foreign policy to which an action, decision, or statement is related.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 28, 2026, 9:55 a.m.