Triple
T26348941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osmanlı Barışı |
E662848
|
entity |
| Predicate | hedefOkurKitlesi |
P85592
|
FINISHED |
| Object | Osmanlı tarihi öğrencileri |
—
|
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: Osmanlı tarihi öğrencileri | Statement: [Osmanlı Barışı, hedefOkurKitlesi, Osmanlı tarihi öğrencileri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hedefOkurKitlesi Context triple: [Osmanlı Barışı, hedefOkurKitlesi, Osmanlı tarihi öğrencileri]
-
A.
readership
Indicates the relationship in which one party reads, follows, or is the audience for the written or published work of another.
-
B.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
C.
targetMarket
Indicates the group of consumers or organizations that a product, service, or campaign is specifically intended and designed to reach.
-
D.
aimedAtBy
Indicates that one entity serves as the target or goal toward which another entity directs an action, intention, or focus.
-
E.
book3Audience
chosen
Indicates that a particular book is intended for or targeted toward a specific audience.
- 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_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 26, 2026, 10:43 p.m.