Triple
T151396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottoman Empire |
E3438
|
entity |
| Predicate | peakTerritorialExtent |
P5049
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Ottoman Empire, peakTerritorialExtent, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakTerritorialExtent Context triple: [Ottoman Empire, peakTerritorialExtent, 16th century]
-
A.
peakTerritorialExtentUnder
Indicates that one entity reached its greatest territorial size or coverage while under the control, rule, or influence of another entity.
-
B.
territorialStatus
Indicates the legal or political condition of control, sovereignty, or jurisdiction that applies to a specific territory.
-
C.
claimsTerritory
Indicates that one entity asserts ownership, control, or sovereign rights over a specific geographic area or region.
-
D.
landArea
Indicates the total surface area of a piece of land associated with an entity, typically measured in standardized units (e.g., square meters, hectares).
-
E.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2580f55a88190b37b54ee0ed5ac7c |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a2565adaf48190b68ae4444ff83ccd |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a256ea776081908fec36c3fdfb8d84 |
completed | Feb. 28, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.