Triple

T35874855
Position Surface form Disambiguated ID Type / Status
Subject Jerusalem Walls National Park E1037329 entity
Predicate hasPart P35 FINISHED
Object Lions’ Gate area
The Lions’ Gate area is a historic section of Jerusalem’s Old City, known as one of its eastern entrances and a key access point to important religious and archaeological sites.
 E2160047 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: Lions’ Gate area | Statement: [Jerusalem Walls National Park, hasPart, Lions’ Gate area]
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: Lions’ Gate area
Triple: [Jerusalem Walls National Park, hasPart, Lions’ Gate area]
Generated description
The Lions’ Gate area is a historic section of Jerusalem’s Old City, known as one of its eastern entrances and a key access point to important religious and archaeological sites.

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_69f76e1e701c8190a4990d4978ce4fe6 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7a9cecbcc81908f354e76f7f06e0b completed May 3, 2026, 8:02 p.m.
NED1 Entity disambiguation (via context triple) batch_6a38a4f0f29c819096590eafd38627f7 completed June 22, 2026, 2:58 a.m.
NEDg Description generation batch_6a38a57d5e2c81908a749015ac6fcd7f completed June 22, 2026, 3:01 a.m.
NED2 Entity disambiguation (via description) batch_6a38a604b0488190a52a2319556ac218 completed June 22, 2026, 3:03 a.m.
Created at: May 3, 2026, 4:06 p.m.