Triple

T1931032
Position Surface form Disambiguated ID Type / Status
Subject Clan Carnegie E40946 entity
Predicate warCry P10430 FINISHED
Object Southesk E40946 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: Southesk | Statement: [Clan Carnegie, warCry, Southesk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Southesk
Context triple: [Clan Carnegie, warCry, Southesk]
  • A. Southesk chosen
    Southesk is the traditional war cry associated with Clan Carnegie, a Scottish noble family from Angus.
  • B. Kinsealy
    Kinsealy is a suburban locality in north County Dublin, Ireland, known for its residential character and proximity to Swords and Dublin city.
  • C. Wauchope
    Wauchope is a rural town in New South Wales, Australia, known as a gateway to the hinterland near Port Macquarie and the surrounding Mid North Coast region.
  • D. Corrsin
    Corrsin is a surname most notably associated with Stanley Corrsin, an influential American fluid dynamicist known for his work on turbulence.
  • E. Muscoy
    Muscoy is an unincorporated community in San Bernardino County, California, known for its semi-rural character within the Inland Empire region.
  • 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_69a8864711648190b07bed24ed76258e completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb296910481908c9668518c09fdb0 completed March 7, 2026, 5:07 a.m.
NED1 Entity disambiguation (via context triple) batch_69adfbb2cc988190a4046c17c8389996 completed March 8, 2026, 10:44 p.m.
Created at: March 4, 2026, 7:35 p.m.