Triple

T20093625
Position Surface form Disambiguated ID Type / Status
Subject Cwmbach E496338 entity
Predicate nearbySettlement P350 FINISHED
Object Aberaman 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: Aberaman | Statement: [Cwmbach, nearbySettlement, Aberaman]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aberaman
Context triple: [Cwmbach, nearbySettlement, Aberaman]
  • A. Aberaman chosen
    Aberaman is a village and community in Rhondda Cynon Taf, Wales, historically associated with coal mining and forming part of the greater Aberdare area.
  • B. Abhramu
    Abhramu is a figure from Hindu and Buddhist mythology known primarily as the consort of the divine elephant Airavati, mount of the god Indra.
  • C. Abas
    Abas is a figure in Greek mythology known primarily as the son of Hypermnestra and a king of Argos in some traditions.
  • D. Abele
    Abele is a surname most notably associated with Julian Abele, a pioneering African American architect who contributed to the design of many prominent buildings in the early 20th century.
  • E. Abiezer
    Abiezer is a biblical figure mentioned in the Hebrew Bible, recognized as an ancestor of the Abiezrite clan associated with the tribe of Manasseh.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69da626eee3881909f3454986d4a6511 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e6666a7a94819080ebabfba9762f97 completed April 20, 2026, 5:46 p.m.
Created at: April 11, 2026, 11:23 p.m.