Triple
T21861265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parrot’s Beak region of Cambodia |
E539765
|
entity |
| Predicate | typeOfBorderFeature |
P69016
|
FINISHED |
| Object | land salient |
—
|
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: land salient | Statement: [Parrot’s Beak region of Cambodia, typeOfBorderFeature, land salient]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfBorderFeature Context triple: [Parrot’s Beak region of Cambodia, typeOfBorderFeature, land salient]
-
A.
bordureType
Indicates the specific style or pattern used for the border or edging of an item or area.
-
B.
formsPartOfBorderType
Indicates that one border type constitutes a component or segment of another, more comprehensive border type.
-
C.
hadBorderType
chosen
Indicates that a boundary between two entities existed and specifies the nature or classification of that border (e.g., land, maritime, disputed).
-
D.
hasBorderFacilityType
Indicates that a border facility possesses or is classified by a specific type or category of border-related infrastructure or service.
-
E.
countryBorderType
Indicates the type or nature of the border relationship that exists between two countries.
- 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_69e0c47829648190bbe2d1d7033768ec |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0d63ae3708190b7ee04c1487713c9 |
completed | April 28, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:56 p.m.