Triple
T29648516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moreh |
E756070
|
entity |
| Predicate | borderTradeStatus |
P195638
|
FINISHED |
| Object | major land customs station |
—
|
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: major land customs station | Statement: [Moreh, borderTradeStatus, major land customs station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderTradeStatus Context triple: [Moreh, borderTradeStatus, major land customs station]
-
A.
borderTradeType
Indicates the specific category or nature of trade that occurs across a border between two regions or countries.
-
B.
borderTradePointWith
Indicates a location or facility where trade or commercial exchange occurs between two bordering regions or countries.
-
C.
borderCityStatus
Indicates that a city holds a designated status due to its location on or near a political or geographic border.
-
D.
hasBorderCrossingStatus
Indicates whether a border crossing is open, closed, restricted, or otherwise classified in terms of its operational or legal status.
-
E.
borderPostIs
Indicates that one entity functions as a border post associated with or located at 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_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
| PDg | Predicate description generation | batch_69fddd364c1481908794c9d423bdc2d7 |
completed | May 8, 2026, 12:55 p.m. |
Created at: April 28, 2026, 6:51 p.m.