Triple
T11374689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balchik |
E269435
|
entity |
| Predicate | wasUnderRomanianRule |
P73014
|
FINISHED |
| Object | 1913–1940 |
—
|
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: 1913–1940 | Statement: [Balchik, wasUnderRomanianRule, 1913–1940]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasUnderRomanianRule Context triple: [Balchik, wasUnderRomanianRule, 1913–1940]
-
A.
wasProtectorateOf
Indicates that one entity was formerly under the protection and partial control of another, typically more powerful, entity.
-
B.
historicallyUnderRuleOf
chosen
Indicates that one entity was historically governed, controlled, or ruled by another entity during a past period.
-
C.
placedUnderAustroHungarianAdministration
Indicates that an entity was brought under the control and governance of the Austro-Hungarian administration for a period of time.
-
D.
underOttomanRuleFrom
Indicates that one entity was under the political authority or control of the Ottoman Empire starting from a specified time.
-
E.
usedInFormerEasternBlocCountry
Indicates that something was used within a country that was part of the former Eastern Bloc.
- 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_69d6aacca1048190b39dbbc2174616fa |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d800160a1c81909d115bf89fe54a49 |
completed | April 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69d7e7022d508190996f9be0847c2b41 |
completed | April 9, 2026, 5:50 p.m. |
Created at: April 8, 2026, 9:33 p.m.