Triple

T3155419
Position Surface form Disambiguated ID Type / Status
Subject Gardens of Vaux-le-Vicomte E65973 entity
Predicate usesDesignPrinciple P1757 FINISHED
Object forced perspective 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: forced perspective | Statement: [Gardens of Vaux-le-Vicomte, usesDesignPrinciple, forced perspective]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesDesignPrinciple
Context triple: [Gardens of Vaux-le-Vicomte, usesDesignPrinciple, forced perspective]
  • A. usesPrinciple chosen
    Indicates that one entity applies, relies on, or is based upon a particular principle in its functioning, reasoning, or design.
  • B. designPhilosophy
    Indicates the guiding principles, values, or conceptual approach that shape how something is designed or created.
  • C. testsPrinciple
    Indicates that an entity evaluates, examines, or challenges the validity or applicability of a principle.
  • D. designedWith
    Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
  • E. reasonForDesign
    Indicates that one entity serves as the explanation, motivation, or justification for why another entity was designed or created in a particular way.
  • 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_69ad8584485081909ed529e890cadc4a completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada5e97548819084643586fff2e3cb completed March 8, 2026, 4:38 p.m.
PD Predicate disambiguation batch_69ad9dfbf0348190952a6bca8fc5fed1 completed March 8, 2026, 4:04 p.m.
Created at: March 8, 2026, 3:05 p.m.