Triple

T13128071
Position Surface form Disambiguated ID Type / Status
Subject Blakstad E311894 entity
Predicate hasReligiousBuilding P1191 FINISHED
Object Froland Church E308957 NE 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: Froland Church | Statement: [Blakstad, hasReligiousBuilding, Froland Church]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Froland Church
Context triple: [Blakstad, hasReligiousBuilding, Froland Church]
  • A. Froland Church chosen
    Froland Church is a historic parish church in Froland, Norway, known for serving as a central religious and cultural landmark for the local community.
  • B. Oura Church
    Oura Church is a historic Catholic church in Nagasaki, Japan, renowned as one of the oldest surviving Christian churches in the country and a symbol of Japan’s hidden Christian heritage.
  • C. Vår Frue Church
    Vår Frue Church is a historic medieval stone church and prominent landmark in central Trondheim, Norway.
  • D. Talgje Church
    Talgje Church is a historic parish church located on the island of Talgje in Rogaland county, Norway.
  • E. Hovin Church
    Hovin Church is a parish church serving the local Church of Norway congregation in Ullensaker, Norway.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d806a9fe888190b081e2d9ea665d6c completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d9819aac388190b59bf43cc6a49d0c completed April 10, 2026, 11:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6e28e922881909584296adc95d9b4 completed May 3, 2026, 5:52 a.m.
Created at: April 9, 2026, 9:07 p.m.