Triple
T5374806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adrianople |
E108934
|
entity |
| Predicate | capitalOfOttomanEmpireUntil |
P13207
|
FINISHED |
| Object | 1453 |
—
|
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: 1453 | Statement: [Adrianople, capitalOfOttomanEmpireUntil, 1453]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalOfOttomanEmpireUntil Context triple: [Adrianople, capitalOfOttomanEmpireUntil, 1453]
-
A.
wasOttomanCity
Indicates that a location previously functioned as a city within the territorial or administrative domain of the Ottoman Empire.
-
B.
caliphateCapital
Indicates that one entity serves as the capital city or administrative center of a particular caliphate.
-
C.
servedAsNationalCapitalUntil
chosen
Indicates that a place functioned as the national capital of a country or state up to a specified end date, after which it no longer held that status.
-
D.
capitalOfRuledEntity
Indicates that a city or settlement serves as the capital of a political entity that rules or governs another entity.
-
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.
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_69bd440c77948190aad2a5f39b7b80f5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd88801b188190b9ac35ed89167fa3 |
completed | March 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69bd846172788190969f24bc7503c05e |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.