Triple

T25833605
Position Surface form Disambiguated ID Type / Status
Subject Porta San Giorgio area E650730 entity
Predicate hasPart P35 FINISHED
Object Porta San Giorgio
Porta San Giorgio is a historic city gate in Florence, Italy, known for marking the southeastern entrance to the old city walls near the road to San Miniato al Monte.
E1704599 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: Porta San Giorgio | Statement: [Porta San Giorgio area, hasPart, Porta San Giorgio]
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: Porta San Giorgio
Triple: [Porta San Giorgio area, hasPart, Porta San Giorgio]
Generated description
Porta San Giorgio is a historic city gate in Florence, Italy, known for marking the southeastern entrance to the old city walls near the road to San Miniato al Monte.

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_69e7ab37438081908f1ccf6284839520 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f601f374308190aebe5dcc12105514 completed May 2, 2026, 1:53 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1107626210819093140b7714c5fb39 completed May 23, 2026, 1:48 a.m.
NEDg Description generation batch_6a1109a47700819082eab631a465c838 completed May 23, 2026, 1:57 a.m.
NED2 Entity disambiguation (via description) batch_6a110a3dc68481909769d05e2c2535bd completed May 23, 2026, 2 a.m.
Created at: April 22, 2026, 7:39 a.m.