Triple
T29648623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zokhawthar |
E756072
|
entity |
| Predicate | hasBorderMarket |
P187383
|
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: [Zokhawthar, hasBorderMarket, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderMarket Context triple: [Zokhawthar, hasBorderMarket, yes]
-
A.
hasMarketBeyond
Indicates that something is sold, demanded, or has commercial presence in regions or markets outside its primary or original one.
-
B.
hasMarket
Indicates that an entity possesses, operates in, or is associated with a particular market or marketplace.
-
C.
hasBorderThrough
Indicates that a border between two regions or entities passes through or along a specified intermediate area, feature, or object.
-
D.
hadBorder
Indicates that one entity shared a common boundary or frontier with another entity during a specified time period.
-
E.
hasBordersBy
Indicates that one entity shares a boundary or border with another entity.
- 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb563a28d88190b28345c465c545f8 |
completed | May 6, 2026, 2:54 p.m. |
Created at: April 28, 2026, 6:51 p.m.