Triple

T36262
Position Surface form Disambiguated ID Type / Status
Subject Redwood National and State Parks E717 entity
Predicate establishedAsNationalPark P856 FINISHED
Object 1968 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: 1968 | Statement: [Redwood National and State Parks, establishedAsNationalPark, 1968]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: establishedAsNationalPark
Context triple: [Redwood National and State Parks, establishedAsNationalPark, 1968]
  • A. protectedAreaEstablished chosen
    Indicates that a designated protected area has been formally created or brought into legal existence.
  • B. designatedNationalHistoricLandmark
    Indicates that an entity has been officially recognized and assigned status as a national historic landmark by the appropriate authority.
  • C. nationalHistoricLandmarkDesignation
    Indicates that an entity has been formally designated as a National Historic Landmark by the appropriate governmental authority.
  • D. addedToNRHP
    Indicates that something has been officially listed on the National Register of Historic Places.
  • E. servedAsUSCapitalUntil
    Indicates that a place functioned as the capital of the United States up to a specified end date.
  • 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_69a247a8f6c08190bac804906d62ed5a completed Feb. 28, 2026, 1:40 a.m.
NER Named-entity recognition batch_69a24bb753f081909cd8b25cfb8e08af completed Feb. 28, 2026, 1:58 a.m.
PD Predicate disambiguation batch_69a24ab4a6908190b6f355415ffe7948 completed Feb. 28, 2026, 1:53 a.m.
Created at: Feb. 28, 2026, 1:46 a.m.