Triple
T28808464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commagene |
E727442
|
entity |
| Predicate | modernProvinces |
P46195
|
FINISHED |
| Object | Adıyaman Province |
—
|
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: Adıyaman Province | Statement: [Commagene, modernProvinces, Adıyaman Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernProvinces Context triple: [Commagene, modernProvinces, Adıyaman Province]
-
A.
modernProvinceLocation
chosen
Indicates that a historical or former province is located within a specified modern administrative province or region.
-
B.
modernRegion
Indicates that an entity is located within or associated with a contemporary, present-day geographic or administrative region.
-
C.
modernNationState
Indicates that an entity functions as a contemporary, centralized political organization with defined territory, governance, and sovereignty recognized as a nation-state.
-
D.
modernPoliticalDivisionIncludes
Indicates that a present-day political or administrative unit geographically contains another political or administrative unit.
-
E.
mainProvinces
Indicates that certain provinces are the primary or most significant administrative regions associated with a given entity.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 28, 2026, 6:30 a.m.