Triple
T18391788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TR-42 |
E449746
|
entity |
| Predicate | standardizedNameFormat |
P39478
|
FINISHED |
| Object | TR-XX pattern for Turkish provinces |
—
|
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: TR-XX pattern for Turkish provinces | Statement: [TR-42, standardizedNameFormat, TR-XX pattern for Turkish provinces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardizedNameFormat Context triple: [TR-42, standardizedNameFormat, TR-XX pattern for Turkish provinces]
-
A.
nameSpellingStandardized
Indicates that an entity’s name has been normalized to a consistent, standardized spelling form.
-
B.
hasStandardizedNameInEnglish
Indicates that an entity is associated with a specific standardized or officially recognized name expressed in English.
-
C.
exportName
Indicates that one entity is exported under a specific name or label in relation to another context or system.
-
D.
nameStyle
chosen
Indicates how an entity’s name is formatted or stylistically presented (e.g., capitalization, punctuation, or naming convention).
-
E.
commonNameOf
Indicates that one entity is the commonly used or popular name by which the other entity is known.
- 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e518435cf481908393c1eb2b4ba659 |
completed | April 19, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:46 a.m.