Triple
T26348783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osmanlı İmparatorluğu'nda Alman Nüfuzu |
E662844
|
entity |
| Predicate | tür |
P160439
|
FINISHED |
| Object | akademik eser |
—
|
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: akademik eser | Statement: [Osmanlı İmparatorluğu'nda Alman Nüfuzu, tür, akademik eser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tür Context triple: [Osmanlı İmparatorluğu'nda Alman Nüfuzu, tür, akademik eser]
-
A.
rok
Indicates a generic, unspecified relationship or interaction between entities labeled by this predicate.
-
B.
taluk
Indicates an administrative relationship where an area or settlement belongs to, is governed by, or falls within the jurisdiction of a specific taluk (sub-district).
-
C.
trap
Indicates that an entity captures, confines, or ensnares another entity, typically preventing its escape or movement.
-
D.
ties
Indicates that one entity fastens, secures, or binds another entity (or two entities together), typically using a flexible connector such as a string, rope, or similar medium.
-
E.
to
Indicates a directional or goal-oriented relationship in which something is directed, transferred, or oriented toward a target or endpoint.
- F. None of above. chosen
Provenance (4 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_69f60fa904a08190938352e5413c1e77 |
completed | May 2, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f6018ceb1c8190a6a5f84071659a96 |
completed | May 2, 2026, 1:52 p.m. |
Created at: April 26, 2026, 10:43 p.m.