Triple
T16936713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TRY |
E410846
|
entity |
| Predicate | subunitNameInTurkish |
P15502
|
FINISHED |
| Object | kuruş |
—
|
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: kuruş | Statement: [TRY, subunitNameInTurkish, kuruş]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subunitNameInTurkish Context triple: [TRY, subunitNameInTurkish, kuruş]
-
A.
nameInTurkish
chosen
Indicates that an entity is known or referred to by a specific name in the Turkish language.
-
B.
subunitNameMeaning
Indicates that a specific name expresses or conveys the meaning or significance of a subunit within a larger entity or structure.
-
C.
subunitType
Indicates that one entity is a specific kind or classification of subunit within the structure or composition of another entity.
-
D.
subunitOf
Indicates that one entity functions as a component or smaller part within the structure or organization of another, larger entity.
-
E.
hasSubunitName
Indicates that an entity includes or is associated with a named subunit or component as part of its structure or organization.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf2adf448190ab0dbebb3addbd80 |
completed | April 18, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.