Triple
T33332398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martunashen |
E853441
|
entity |
| Predicate | hasDeFactoLocationContext |
P198366
|
FINISHED |
| Object | Nagorno-Karabakh conflict zone |
—
|
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: Nagorno-Karabakh conflict zone | Statement: [Martunashen, hasDeFactoLocationContext, Nagorno-Karabakh conflict zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeFactoLocationContext Context triple: [Martunashen, hasDeFactoLocationContext, Nagorno-Karabakh conflict zone]
-
A.
hasLocalContext
Indicates that something exists or occurs within a specific, surrounding situational or environmental context tied to a particular place or scope.
-
B.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
-
C.
hasLocationFocus
Indicates that the primary emphasis or relevance of something is centered on a specific location or place.
-
D.
hasActLocation
Indicates that an action or event occurs at, or is associated with, a specific location.
-
E.
hasLocationRole
Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
- F. None of above. chosen
Provenance (4 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fedfd913f48190bdcd450980868d9a |
completed | May 9, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fedf58c6e88190821a7156054c9086 |
completed | May 9, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69fedfd850ec81909b55f90dc850167e |
completed | May 9, 2026, 7:18 a.m. |
Created at: May 1, 2026, 1:34 a.m.