Triple
T30517350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suruç |
E776600
|
entity |
| Predicate | hasProvinceISOCode |
P99880
|
FINISHED |
| Object | TR-63 |
—
|
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-63 | Statement: [Suruç, hasProvinceISOCode, TR-63]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProvinceISOCode Context triple: [Suruç, hasProvinceISOCode, TR-63]
-
A.
hasProvinceOrRegion
Indicates that one entity includes, is associated with, or is located within a specific province or region as an administrative or geographic subdivision.
-
B.
hasProvinceName
Indicates that an entity (such as a province or region) bears or is associated with a specific province name.
-
C.
hasProvinceEquivalent
Indicates that one administrative division is equivalent in status or function to a province within a given political or territorial system.
-
D.
hasProvinceType
Indicates that an entity is associated with a province classified by a specific type or category.
-
E.
hasProvincialCode
chosen
Indicates that an entity is associated with a specific provincial code that identifies its province or administrative region.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ffef812da48190b875a7376b24f92d |
completed | May 10, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69ffedecd580819097851b1473fdd6ed |
completed | May 10, 2026, 2:31 a.m. |
Created at: April 29, 2026, 8:16 p.m.