Triple
T19063819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saudi Arabia–Bahrain border |
E466602
|
entity |
| Predicate | isShortComparedTo |
P34871
|
FINISHED |
| Object | other Saudi Arabia international borders |
—
|
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: other Saudi Arabia international borders | Statement: [Saudi Arabia–Bahrain border, isShortComparedTo, other Saudi Arabia international borders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isShortComparedTo Context triple: [Saudi Arabia–Bahrain border, isShortComparedTo, other Saudi Arabia international borders]
-
A.
isShort
chosen
Indicates that one entity has a relatively small height, length, or duration compared to a standard or to other entities.
-
B.
isShortName
Indicates that one name is an abbreviated or shorter form of another name.
-
C.
isShallowComparedTo
Indicates that one entity has less depth or is less profound than another entity when compared.
-
D.
hasShort
Indicates that an entity possesses or is characterized by something of short length or duration.
-
E.
hasShorterDurationThan
Indicates that the duration of one event or interval is less than the duration of another.
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e196deac8190ad0406c616197e0b |
completed | April 20, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.