Triple
T10448629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urfa region |
E246357
|
entity |
| Predicate | wasSignificantCenterOf |
P164
|
FINISHED |
| Object | Christian communities |
—
|
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: Christian communities | Statement: [Urfa region, wasSignificantCenterOf, Christian communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasSignificantCenterOf Context triple: [Urfa region, wasSignificantCenterOf, Christian communities]
-
A.
historicallyImportantCenter
Indicates that a place has served as a significant focal point of historical events, activities, or influence.
-
B.
hasMajorHistoricalCentersIn
Indicates that an entity possesses significant, historically important centers or hubs located within a specified place or region.
-
C.
isMajorCenterOf
chosen
Indicates that a place serves as a primary hub or focal point for a particular activity, function, or domain.
-
D.
wasImportantCityOf
Indicates that a city held significant importance or prominence within a specified larger political or geographic entity during a given time period.
-
E.
wasMajorCenterDuring
Indicates that a place served as a primary or highly significant hub of activity, influence, or importance during a specified time period.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe083cd881909d2d8ad75d1d94cb |
completed | April 7, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69d4fb73a5e48190a8df4775bc5da80f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:16 p.m.