Triple

T24427154
Position Surface form Disambiguated ID Type / Status
Subject Battle of Iron Hill E615890 entity
Predicate geographicalFeature P5378 FINISHED
Object Cooch’s Bridge
Cooch’s Bridge is a historic site in Delaware known as the location of a key Revolutionary War skirmish and the only major battle fought in the state.
E1635307 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: Cooch’s Bridge | Statement: [Battle of Iron Hill, geographicalFeature, Cooch’s Bridge]
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: Cooch’s Bridge
Triple: [Battle of Iron Hill, geographicalFeature, Cooch’s Bridge]
Generated description
Cooch’s Bridge is a historic site in Delaware known as the location of a key Revolutionary War skirmish and the only major battle fought in the state.

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_69e2d7eadb248190a867130fe45f0388 completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f296a84c848190bce2c004a667dbe7 completed April 29, 2026, 11:39 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0fe37021c881908698d20d069feacc completed May 22, 2026, 5:02 a.m.
NEDg Description generation batch_6a0fe5a2147081908aa1e8c513d80463 completed May 22, 2026, 5:12 a.m.
NED2 Entity disambiguation (via description) batch_6a0fe620e40c81909973369ffb8e9dfc completed May 22, 2026, 5:14 a.m.
Created at: April 18, 2026, 2:15 a.m.