Triple

T24323563
Position Surface form Disambiguated ID Type / Status
Subject Parish of Nossa Senhora da Luz E613034 entity
Predicate isToponymicSourceOf P19572 FINISHED
Object Luz (in Estádio da Luz) 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: Luz (in Estádio da Luz) | Statement: [Parish of Nossa Senhora da Luz, isToponymicSourceOf, Luz (in Estádio da Luz)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isToponymicSourceOf
Context triple: [Parish of Nossa Senhora da Luz, isToponymicSourceOf, Luz (in Estádio da Luz)]
  • A. isToponymIn
    Indicates that a place name (toponym) is located within or refers to a specific geographic area or region.
  • B. toponymSourceFor chosen
    Indicates that one entity serves as the origin, basis, or source from which another entity’s place name (toponym) is derived.
  • C. toponymRefersTo
    Indicates that a place name (toponym) designates or refers to a specific geographic entity or location.
  • D. hasOriginToponym
    Indicates that something originates from, or is derived from, the place denoted by a specific toponym (geographical name).
  • E. hasToponymicAssociation
    Indicates a relationship where one entity is associated with, derived from, or named after a particular place or geographic name (toponym).
  • F. None of above.

Provenance (3 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_69e2d7db6d5c819091194918157a7c1f completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f292ae127881909ef1772278181ce3 completed April 29, 2026, 11:22 p.m.
PD Predicate disambiguation batch_69f287ad30048190b3ad3613486f277f completed April 29, 2026, 10:35 p.m.
Created at: April 18, 2026, 1:53 a.m.