Triple
T25825116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No Hands Bridge |
E650506
|
entity |
| Predicate | riverBranch |
P163702
|
FINISHED |
| Object | North Fork of the American River |
—
|
NE NERFINISHED |
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 Fork of the American River | Statement: [No Hands Bridge, riverBranch, North Fork of the American River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverBranch Context triple: [No Hands Bridge, riverBranch, North Fork of the American River]
-
A.
riverBankTwo
Indicates a relationship where something is located on or associated with the second of two identified banks of a river.
-
B.
riverBankOne
Indicates that the referenced entity is one specific side or bank of a river, typically the first or primary one in a pairwise relation.
-
C.
isSouthernBranchOf
Indicates that one entity functions as the southern subdivision or regional branch of another, larger organization or structure.
-
D.
riverBankOnSouthSide
Indicates that a river bank is located on the southern side of a specified river or watercourse.
-
E.
branchNetwork
Indicates that one entity operates as a branch or local outlet within the wider organizational or operational network of 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6397b64f881909d811225e57aac5e |
completed | May 2, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f638d029148190877c103f0eeaf147 |
completed | May 2, 2026, 5:48 p.m. |
Created at: April 22, 2026, 7:32 a.m.