Triple

T26788887
Position Surface form Disambiguated ID Type / Status
Subject Mesita A E670460 entity
Predicate relativeImportanceWithinPark P89351 FINISHED
Object principal terrace complex 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: principal terrace complex | Statement: [Mesita A, relativeImportanceWithinPark, principal terrace complex]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relativeImportanceWithinPark
Context triple: [Mesita A, relativeImportanceWithinPark, principal terrace complex]
  • A. regionOfPark
    Indicates that one entity is a geographic or administrative region that contains or is designated as a specific park.
  • B. localImportance chosen
    Indicates that something holds particular significance, influence, or priority within a specific, limited context or area rather than globally.
  • C. withinNationalPark
    Indicates that one entity is located inside the geographic boundaries of a national park designated by another entity.
  • D. recreationalImportance
    Indicates the degree to which something is valued or used for leisure, play, or recreational activities.
  • E. locatedInNationalParkOrQuasiNationalPark
    Indicates that something is situated within the boundaries of a national park or a quasi-national park.
  • 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_69eeb31d45f8819089f52ebdbc556218 completed April 27, 2026, 12:51 a.m.
NER Named-entity recognition batch_69fecd0a732c819097bdd3eb69b6158c completed May 9, 2026, 5:58 a.m.
PD Predicate disambiguation batch_69fecc0318d481908b5b20598a76a9fe completed May 9, 2026, 5:54 a.m.
Created at: April 27, 2026, 4:15 a.m.