Triple
T26087306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coron |
E658017
|
entity |
| Predicate | formerNameUnderOttomans |
P143260
|
FINISHED |
| Object | Koron |
—
|
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: Koron | Statement: [Coron, formerNameUnderOttomans, Koron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerNameUnderOttomans Context triple: [Coron, formerNameUnderOttomans, Koron]
-
A.
OttomanName
chosen
Indicates that an entity has a name or designation used during the Ottoman Empire period.
-
B.
underOttomanRuleFrom
Indicates that one entity was under the political authority or control of the Ottoman Empire starting from a specified time.
-
C.
countryDuringOttomanUse
Indicates that a specified country existed or held authority over a place or entity during the period of Ottoman rule or influence.
-
D.
modernNameInTurkish
Indicates that an entity is known by a specific modern Turkish name.
-
E.
historicalRegionOnOttomanSide
Indicates that a historical region was aligned with, controlled by, or part of the Ottoman side in a particular conflict, division, or political context.
- 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 26, 2026, 7:44 p.m.