Triple
T33332371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goranboy District |
E853440
|
entity |
| Predicate | hasFrontlineAreas |
P53598
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Goranboy District, hasFrontlineAreas, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFrontlineAreas Context triple: [Goranboy District, hasFrontlineAreas, yes]
-
A.
frontLineRegion
chosen
Indicates that a region is located at or constitutes the primary area of direct engagement or contact in a conflict, competition, or critical situation.
-
B.
hasFrontLineFeature
Indicates that an entity possesses a specific characteristic or element located on its front side or leading edge.
-
C.
hasRunoffAreas
Indicates that an entity includes or is equipped with designated runoff areas for managing excess water or liquid flow.
-
D.
frontlineAdvance
Indicates a movement of military or conflict front lines forward into previously uncontrolled or enemy-held territory.
-
E.
frontlineUse
Indicates that something is used as the primary or first-line option in addressing a problem, condition, or situation.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: May 1, 2026, 1:34 a.m.