Triple
T34843042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qatar Peninsula |
E1004391
|
entity |
| Predicate | borderDirectionFromSaudiArabia |
P200134
|
FINISHED |
| Object | north |
—
|
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: north | Statement: [Qatar Peninsula, borderDirectionFromSaudiArabia, north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDirectionFromSaudiArabia Context triple: [Qatar Peninsula, borderDirectionFromSaudiArabia, north]
-
A.
borderTypeToSaudiArabia
Indicates the type or nature of the border that an entity shares with Saudi Arabia.
-
B.
borderDirectionFromUS
Indicates the compass direction in which a country or region lies relative to the United States along their shared border.
-
C.
borderDirectionFromCapital
Indicates the compass direction from a country's capital city to a specified border or neighboring entity.
-
D.
borderDirectionFromSingapore
Indicates the directional orientation of another location’s border relative to Singapore.
-
E.
borderDirectionRelativeToEbebiyín
Indicates the compass direction in which a given entity’s border lies relative to the location of Ebebiyín.
- 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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff76ac40988190a34d858b5472ee2b |
completed | May 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69ff760a90948190a12fcb80e6e3e14b |
completed | May 9, 2026, 5:59 p.m. |
| PDg | Predicate description generation | batch_69ff76ab9b4c8190b4cc7c9c733b2765 |
completed | May 9, 2026, 6:02 p.m. |
Created at: May 3, 2026, 4 p.m.