Triple

T18605020
Position Surface form Disambiguated ID Type / Status
Subject Porta Faul E454719 entity
Predicate hasName P744 FINISHED
Object Porta Faul NE NERFINISHED

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 Faul | Statement: [Porta Faul, hasName, Porta Faul]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Porta Faul
Context triple: [Porta Faul, hasName, Porta Faul]
  • A. Porta Faul chosen
    Porta Faul is a historic city gate in Viterbo, Italy, notable as part of the town’s medieval defensive walls.
  • B. Carmental Gate
    Carmental Gate was an ancient city gate in Rome’s early defensive walls, serving as a key western entrance near the Tiber and associated with important religious and historical traditions.
  • C. Porta Uzeda
    Porta Uzeda is a historic Baroque city gate in Catania, Italy, forming a monumental entrance between the old city center and the seafront.
  • D. Porta Grande
    Porta Grande is a historic city gate and notable architectural landmark in the town of Mesagne in southern Italy.
  • E. Porta Elisa
    Porta Elisa is a neoclassical city gate in Lucca, Italy, serving as one of the main entrances through the town’s historic defensive walls.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8d38bbe7c8190bdec3138e7d413c9 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e547535b8c8190ab5a8a92f15f2bcb completed April 19, 2026, 9:21 p.m.
Created at: April 10, 2026, 11:45 a.m.