Triple
T26348937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osmanlı Barışı |
E662848
|
entity |
| Predicate | incelediğiKavram |
P160442
|
FINISHED |
| Object | imparatorluk içi denge politikaları |
—
|
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: imparatorluk içi denge politikaları | Statement: [Osmanlı Barışı, incelediğiKavram, imparatorluk içi denge politikaları]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incelediğiKavram Context triple: [Osmanlı Barışı, incelediğiKavram, imparatorluk içi denge politikaları]
-
A.
incelediğiKavram
chosen
Indicates that an entity examines, studies, or analyzes a particular concept.
-
B.
dil
Indicates that one entity is diluted or made less concentrated by another entity or process.
-
C.
inlaidWith
Indicates that one object has decorative material set into its surface, typically flush with it, using a contrasting substance or pattern.
-
D.
isin
Indicates that one entity is contained within, or is a member of, another entity or set.
-
E.
kokudaka
Indicates a relationship where a landholding or domain is assigned a value based on its assessed agricultural productivity or tax yield, typically measured in koku.
- 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60fa9dc9c8190b2501a3bc23eabfe |
completed | May 2, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 10:43 p.m.