Triple
T23899784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Angora |
E601008
|
entity |
| Predicate | OttomanDynasty |
P153996
|
FINISHED |
| Object | House of Osman |
—
|
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: House of Osman | Statement: [Battle of Angora, OttomanDynasty, House of Osman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OttomanDynasty Context triple: [Battle of Angora, OttomanDynasty, House of Osman]
-
A.
OttomanRole
Indicates that an entity holds or held a specific role, position, or function within the Ottoman Empire.
-
B.
OttomanName
Indicates that an entity has a name or designation used during the Ottoman Empire period.
-
C.
OttomanStrength
Indicates the level or degree of military, political, or economic power possessed or exerted by the Ottoman Empire in a given context.
-
D.
countryDuringOttomanUse
Indicates that a specified country existed or held authority over a place or entity during the period of Ottoman rule or influence.
-
E.
underOttomanRuleFrom
Indicates that one entity was under the political authority or control of the Ottoman Empire starting from a specified time.
- 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_69e295341ac0819080647f2908af793c |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cdddca088190b6c26df984a143ad |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 8:25 p.m.