Triple

T24218958
Position Surface form Disambiguated ID Type / Status
Subject Camp Furlong E601391 entity
Predicate locatedIn P40 FINISHED
Object Columbus, New Mexico
Columbus, New Mexico is a small village near the U.S.–Mexico border best known as the site of Pancho Villa’s 1916 raid and the subsequent U.S. military response.
E1626733 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: Columbus, New Mexico | Statement: [Camp Furlong, locatedIn, Columbus, New Mexico]
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: Columbus, New Mexico
Triple: [Camp Furlong, locatedIn, Columbus, New Mexico]
Generated description
Columbus, New Mexico is a small village near the U.S.–Mexico border best known as the site of Pancho Villa’s 1916 raid and the subsequent U.S. military response.

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_69e29537ca548190b94a37ebe1977caf completed April 17, 2026, 8:16 p.m.
NER Named-entity recognition batch_69f2820b9c808190b6f9201e4b2e85c2 completed April 29, 2026, 10:11 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0fc9b01dcc81909ee11123eac678f9 completed May 22, 2026, 3:12 a.m.
NEDg Description generation batch_6a0fcac04c188190ae575dc3b2696e65 completed May 22, 2026, 3:17 a.m.
NED2 Entity disambiguation (via description) batch_6a0fcb321b288190987dc5bb92a6fc2d completed May 22, 2026, 3:19 a.m.
Created at: April 17, 2026, 11:59 p.m.