Triple

T21045620
Position Surface form Disambiguated ID Type / Status
Subject Villa Badoer E518439 entity
Predicate hasSymmetricalPlan P50368 FINISHED
Object yes LITERAL 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: yes | Statement: [Villa Badoer, hasSymmetricalPlan, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSymmetricalPlan
Context triple: [Villa Badoer, hasSymmetricalPlan, yes]
  • A. isSymmetrical chosen
    Indicates that an object, pattern, or configuration remains unchanged or mirrored when transformed by a symmetry operation such as reflection, rotation, or inversion.
  • B. isSymmetricAbout
    Indicates that one entity is a mirror image of another with respect to a specified axis, point, or plane of symmetry.
  • C. symmetryOf
    Indicates that one entity is the symmetry counterpart or symmetric form of another entity, typically related by a specific symmetry operation or transformation.
  • D. isSymmetric
    Indicates that a relationship holds in both directions between two entities, so if it applies from A to B, it also applies from B to A.
  • E. symmetryInvolved
    Indicates that a relationship or action inherently involves symmetry, such as invariance under certain transformations or the presence of symmetric structure or behavior.
  • 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_69e0b50438e08190917e2538bb8bc034 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e6fcf3cac081909915a440fbb5c084 completed April 21, 2026, 4:28 a.m.
PD Predicate disambiguation batch_69e5dbf6728881908a2a43a5c8804a2a completed April 20, 2026, 7:55 a.m.
Created at: April 16, 2026, 2:32 p.m.