Triple
T17001655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Am |
E412458
|
entity |
| Predicate | associatedWith |
P37
|
FINISHED |
| Object | Ambridge village |
E1236975
|
NE 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: Ambridge village | Statement: [River Am, associatedWith, Ambridge village]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ambridge village Context triple: [River Am, associatedWith, Ambridge village]
-
A.
Ambridge
Ambridge is a small industrial borough in western Pennsylvania known historically for its steel production and connection to the American Bridge Company.
-
B.
Ambridge
chosen
Ambridge is the fictional English village that serves as the primary setting for the long-running BBC radio drama "The Archers."
-
C.
Bethel Park
Bethel Park is a suburban municipality in southwestern Pennsylvania, located just south of Pittsburgh.
-
D.
Malville
Malville is a commune in western France located within the Loire-Atlantique department.
-
E.
Beaver Falls
Beaver Falls is a small industrial city in western Pennsylvania known historically for its manufacturing base and location along the Beaver River.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d37ec2b48190b4f997899d887ba8 |
completed | April 18, 2026, 6:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01413a445c8190920fe385d3cd43f3 |
completed | May 11, 2026, 2:38 a.m. |
Created at: April 10, 2026, 5:32 a.m.