Triple
T33400854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kara Qorum region |
E855292
|
entity |
| Predicate | sourceDisagreement |
P14608
|
FINISHED |
| Object | extent of region |
—
|
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: extent of region | Statement: [Kara Qorum region, sourceDisagreement, extent of region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceDisagreement Context triple: [Kara Qorum region, sourceDisagreement, extent of region]
-
A.
disputed
Indicates that there is active disagreement or contestation over the validity, ownership, interpretation, or status of the relationship or claim between the entities.
-
B.
hasSourceOfDebate
Indicates that something is the origin or cause of an ongoing disagreement, controversy, or dispute between parties.
-
C.
conflictSource
Indicates that one entity is the origin, cause, or initiating side of a conflict involving another entity.
-
D.
disputedAspect
chosen
Indicates that a particular feature, detail, or component of something is subject to disagreement or contention between parties.
-
E.
disputedInterpretation
Indicates that there is disagreement or contention over how something should be understood, interpreted, or explained.
- 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: May 1, 2026, 1:35 a.m.