Triple
T5810128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Little Rock, Arkansas |
E128846
|
entity |
| Predicate | isLocatedOnBankOf |
P7935
|
FINISHED |
| Object | north bank of the Arkansas River |
—
|
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 bank of the Arkansas River | Statement: [North Little Rock, Arkansas, isLocatedOnBankOf, north bank of the Arkansas River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedOnBankOf Context triple: [North Little Rock, Arkansas, isLocatedOnBankOf, north bank of the Arkansas River]
-
A.
hasLandmarkOnBank
Indicates that a landmark is located on the bank (shore or edge) of a geographic feature such as a river, lake, or canal.
-
B.
locatedOnBankOfRiver
Indicates that one entity is situated along or directly adjacent to the bank of a specified river.
-
C.
hasCityOnBank
chosen
Indicates that a city is located on the bank of a particular river or body of water.
-
D.
hasParkAlongBank
Indicates that a park is located adjacent to or running alongside the bank of a water body.
-
E.
isLocatedOn
Indicates that one entity exists at or is situated upon the surface or area of another entity.
- 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_69c0084788848190bcf71f6bc5d71597 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b52663c8190ab44258468d4296d |
completed | March 22, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c021d5ecd081908a62dd66e26f8598 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:52 p.m.