Triple

T33490467
Position Surface form Disambiguated ID Type / Status
Subject Issus E857723 entity
Predicate watercourseNearby P8567 FINISHED
Object Pinarus River
The Pinarus River is an ancient waterway in southern Anatolia, historically significant as the site near which Alexander the Great defeated Darius III at the Battle of Issus in 333 BCE.
E2189199 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: Pinarus River | Statement: [Issus, watercourseNearby, Pinarus River]
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: Pinarus River
Triple: [Issus, watercourseNearby, Pinarus River]
Generated description
The Pinarus River is an ancient waterway in southern Anatolia, historically significant as the site near which Alexander the Great defeated Darius III at the Battle of Issus in 333 BCE.

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_69f3497547608190a1a0f2365fb713ee completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6e565dc0481908b03d4d0d8ec7d5d completed May 3, 2026, 6:04 a.m.
NED1 Entity disambiguation (via context triple) batch_6a39e6ba1eec8190ba260a785674260a completed June 23, 2026, 1:51 a.m.
NEDg Description generation batch_6a39e9200b58819098d74fb83545bbe1 completed June 23, 2026, 2:02 a.m.
NED2 Entity disambiguation (via description) batch_6a39ea1724308190bf47c548635429ca completed June 23, 2026, 2:06 a.m.
Created at: May 1, 2026, 1:38 a.m.