Triple

T31881985
Position Surface form Disambiguated ID Type / Status
Subject Assyrian province of Dor E813905 entity
Predicate archaeologicalEvidenceAt P16255 FINISHED
Object Tel Dor
Tel Dor is an important archaeological mound on Israel’s Mediterranean coast, preserving remains from Canaanite, Phoenician, Israelite, Persian, Hellenistic, and Roman periods.
E1981508 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: Tel Dor | Statement: [Assyrian province of Dor, archaeologicalEvidenceAt, Tel Dor]
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: Tel Dor
Triple: [Assyrian province of Dor, archaeologicalEvidenceAt, Tel Dor]
Generated description
Tel Dor is an important archaeological mound on Israel’s Mediterranean coast, preserving remains from Canaanite, Phoenician, Israelite, Persian, Hellenistic, and Roman periods.

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_69f348ed74bc81909846aaa6a3c7318c completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6b0d697c881909520acc306c026eb completed May 3, 2026, 2:20 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2e7fe35f808190b2568f1bfcf23359 completed June 14, 2026, 10:18 a.m.
NEDg Description generation batch_6a2e805933e88190a0138549f9de49a7 completed June 14, 2026, 10:20 a.m.
NED2 Entity disambiguation (via description) batch_6a2e80d3e0c88190bc0974a86e6f3dff completed June 14, 2026, 10:22 a.m.
Created at: April 30, 2026, 11:56 p.m.