Triple

T31220553
Position Surface form Disambiguated ID Type / Status
Subject Porta Salutaris E795997 entity
Predicate locatedIn P40 FINISHED
Object Alta Semita area
The Alta Semita area was an ancient district on Rome’s Quirinal Hill, known for its major thoroughfare and concentration of important buildings and gates in the early city.
E1952349 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: Alta Semita area | Statement: [Porta Salutaris, locatedIn, Alta Semita 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: Alta Semita area
Triple: [Porta Salutaris, locatedIn, Alta Semita area]
Generated description
The Alta Semita area was an ancient district on Rome’s Quirinal Hill, known for its major thoroughfare and concentration of important buildings and gates in the early city.

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_69f224d9d52c8190a61f68ded37fa755 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f69c4d35848190bd5a2dd81851bea3 completed May 3, 2026, 12:52 a.m.
NED1 Entity disambiguation (via context triple) batch_6a29592d54d08190b756f6dc853d4faa completed June 10, 2026, 12:31 p.m.
NEDg Description generation batch_6a2959e9572c8190b8d3f16d5203050a completed June 10, 2026, 12:34 p.m.
NED2 Entity disambiguation (via description) batch_6a295c5a2ec481909a153eaf63de517d completed June 10, 2026, 12:45 p.m.
Created at: April 29, 2026, 9:10 p.m.