Triple
T30896710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sultan Husayn |
E787039
|
entity |
| Predicate | foreignPressure |
P32209
|
FINISHED |
| Object | Ottoman Empire |
—
|
NE NERFINISHED |
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: Ottoman Empire | Statement: [Sultan Husayn, foreignPressure, Ottoman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foreignPressure Context triple: [Sultan Husayn, foreignPressure, Ottoman Empire]
-
A.
foreignInfluence
chosen
Indicates that one entity exerts influence, control, or significant impact on another entity from a different country or external origin.
-
B.
foreignPolicyArea
Indicates the specific domain or topic within foreign policy to which an action, decision, or statement is related.
-
C.
foreignPolicyCoordinationWith
Indicates that one entity collaborates with another to align, coordinate, or jointly manage their foreign policy positions, strategies, or actions.
-
D.
foreignPolicyEvent
Indicates an event involving actions, decisions, or developments in a state’s relations with other countries or international actors.
-
E.
countryImposing
Indicates that one country is applying or enforcing a measure, rule, or sanction upon 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6923c906c81908450147ba40dfeec |
completed | May 3, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:49 p.m.