Triple
T6354380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottoman Beylik |
E142953
|
entity |
| Predicate | expansionDirection |
P64848
|
FINISHED |
| Object | westward into Byzantine territory |
—
|
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: westward into Byzantine territory | Statement: [Ottoman Beylik, expansionDirection, westward into Byzantine territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionDirection Context triple: [Ottoman Beylik, expansionDirection, westward into Byzantine territory]
-
A.
plannedExtensionDirection
Indicates the intended directional path or orientation along which something is planned to be extended in the future.
-
B.
expansionType
Indicates the specific manner or category by which something grows, extends, or increases in scope or size.
-
C.
expandsIn
Indicates that one entity grows, spreads, or extends its presence or influence within the space, scope, or context defined by another entity.
-
D.
territorialExpansionDirection
chosen
Indicates the primary geographic direction in which an entity’s territory is expanding or has expanded.
-
E.
trajectoryExpansion
Indicates how the path or course of something spreads, widens, or diversifies over time or space.
- 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_69c008d6dcbc8190aa1c2f1fd8916b42 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c067e0cf1081908ee7e83b9dcf740e |
completed | March 22, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69c060ec091c8190912aac44e1b8b1c9 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:31 p.m.