Triple
T5843113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mobile County |
E129640
|
entity |
| Predicate | namedFor |
P63
|
FINISHED |
| Object | Mobile River |
E174358
|
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: Mobile River | Statement: [Mobile County, namedFor, Mobile River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mobile River Context triple: [Mobile County, namedFor, Mobile River]
-
A.
Mobile River
chosen
The Mobile River is a major waterway in southwestern Alabama that flows into Mobile Bay and serves as an important channel for commerce and transportation.
-
B.
Save River
The Save River is a major waterway in southeastern Africa that flows through Zimbabwe and Mozambique before emptying into the Indian Ocean.
-
C.
River Can
River Can is a small river in Essex, England, that flows through the city of Chelmsford and forms part of the River Chelmer system.
-
D.
Pages River
Pages River is a minor river in New South Wales, Australia, that forms part of the Hunter River catchment.
-
E.
Turbo River
Turbo River is a waterway in northwestern Colombia that runs through the municipality of Turbo in the Antioquia Department and drains into the Gulf of Urabá in the Caribbean Sea.
- 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_69c0084bd31c8190a796bb6284845e83 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c034d9da0c8190970319d0dc2fc73f |
completed | March 22, 2026, 6:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0a1a2506481908a3e638c1121bfd0 |
completed | March 23, 2026, 2:12 a.m. |
Created at: March 22, 2026, 3:54 p.m.