Triple

T1584079
Position Surface form Disambiguated ID Type / Status
Subject Mobile, Alabama E34031 entity
Predicate locatedOnRiver P165 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, Alabama, locatedOnRiver, Mobile River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mobile River
Context triple: [Mobile, Alabama, locatedOnRiver, 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. Pages River
    Pages River is a minor river in New South Wales, Australia, that forms part of the Hunter River catchment.
  • C. Ourthe River
    The Ourthe River is a major watercourse in southeastern Belgium that flows through the Ardennes region before joining the Meuse River.
  • D. Tech River
    Tech River is a river in southern France that flows through the Pyrénées-Orientales department before emptying into the Mediterranean Sea.
  • E. River Suck
    River Suck is a major river in western Ireland that flows through counties such as Roscommon and Galway before joining the River Shannon.
  • 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_69a885fceb2c8190b47e0f7c0aefbff0 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a908f0e72c8190bb7a2a0c77379060 completed March 5, 2026, 4:39 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad4698cde88190a113cb7cebc3df1e completed March 8, 2026, 9:51 a.m.
Created at: March 4, 2026, 7:27 p.m.