Triple

T37805845
Position Surface form Disambiguated ID Type / Status
Subject English Civil War operations in southern England E942495 entity
Predicate involvedRegion P285 FINISHED
Object Kent
Kent is a historic county in southeastern England that played a notable role as a theater of conflict and strategic importance during the English Civil War.
E5977 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: Kent | Statement: [English Civil War operations in southern England, involvedRegion, Kent]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Kent
Triple: [English Civil War operations in southern England, involvedRegion, Kent]
Generated description
Kent is a historic county in southeastern England that played a notable role as a theater of conflict and strategic importance during the English Civil War.

Provenance (5 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_69f76ee8104c8190ab17133ccd8f86e6 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fbb197983c8190b367cf4a5486bd13 completed May 6, 2026, 9:24 p.m.
NED1 Entity disambiguation (via context triple) batch_6a40f178dea4819092ef0f7be9da3f30 completed June 28, 2026, 10:03 a.m.
NEDg Description generation batch_6a40f211fc1c8190921fb8b63b0fd264 completed June 28, 2026, 10:06 a.m.
NED2 Entity disambiguation (via description) batch_6a40f27a9364819088f0f6bcfffa44b2 completed June 28, 2026, 10:07 a.m.
Created at: May 3, 2026, 4:19 p.m.