Triple
T35230062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ankara Governorship |
E1017207
|
entity |
| Predicate | overseesDistrict |
P153241
|
FINISHED |
| Object | Nallıhan |
—
|
NE NERFINISHED |
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: Nallıhan | Statement: [Ankara Governorship, overseesDistrict, Nallıhan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overseesDistrict Context triple: [Ankara Governorship, overseesDistrict, Nallıhan]
-
A.
overseesCounty
Indicates that one administrative or governing entity has supervisory or managerial authority over a specific county.
-
B.
overseesDivision
Indicates that one entity has managerial or supervisory responsibility over a specific division of an organization.
-
C.
overseesRegionKnownAs
chosen
Indicates that an entity has managerial or supervisory authority over a region identified by a specific name.
-
D.
oversawArea
Indicates that one entity had supervisory or managerial responsibility over a particular area, region, or domain associated with another entity.
-
E.
governmentalDistrictOf
Indicates that a governmental district is the administrative district to which a given entity belongs or in which it is located.
- 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_69f76de12e4c8190bc46b71a32858356 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:02 p.m.