Triple
T10321725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tur Abdin |
E242151
|
entity |
| Predicate | presentDayIssue |
P40848
|
FINISHED |
| Object | cultural and property rights disputes involving monasteries |
—
|
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: cultural and property rights disputes involving monasteries | Statement: [Tur Abdin, presentDayIssue, cultural and property rights disputes involving monasteries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentDayIssue Context triple: [Tur Abdin, presentDayIssue, cultural and property rights disputes involving monasteries]
-
A.
currentIssue
Indicates that an entity is the presently relevant or active issue in a given context or discussion.
-
B.
modernIssue
chosen
Indicates that the subject is a contemporary or current-day issue affecting the object or broader context.
-
C.
presentDayRemains
Indicates that something from the past still exists or has surviving traces in the present day.
-
D.
presentDayControl
Indicates that one entity currently holds authority, governance, or control over another entity in the present day.
-
E.
currentChallenges
Indicates the difficulties or obstacles an entity is presently facing or dealing with.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:50 a.m.