Triple

T33244454
Position Surface form Disambiguated ID Type / Status
Subject Battle of Mount Scorobas E851055 entity
Predicate location P40 FINISHED
Object Mount Scorobas
Mount Scorobas is an ancient battlefield site in Asia Minor, known primarily as the location of a significant engagement during the Roman–Seleucid conflicts.
E2066890 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: Mount Scorobas | Statement: [Battle of Mount Scorobas, location, Mount Scorobas]
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: Mount Scorobas
Triple: [Battle of Mount Scorobas, location, Mount Scorobas]
Generated description
Mount Scorobas is an ancient battlefield site in Asia Minor, known primarily as the location of a significant engagement during the Roman–Seleucid conflicts.

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_69f34962386c81909ddc3bf9e18ddeb8 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6daf29a68819095b81e0fd46ae729 completed May 3, 2026, 5:19 a.m.
NED1 Entity disambiguation (via context triple) batch_6a36655d84148190a05cf421ed2f6356 completed June 20, 2026, 10:03 a.m.
NEDg Description generation batch_6a366626e0708190b7b11d854a951965 completed June 20, 2026, 10:06 a.m.
NED2 Entity disambiguation (via description) batch_6a3666c1d1b881908654acaa4b5898ec completed June 20, 2026, 10:09 a.m.
Created at: May 1, 2026, 1:31 a.m.