Triple

T13387343
Position Surface form Disambiguated ID Type / Status
Subject church at Brattahlid E319477 entity
Predicate timeDepthRepresented P40474 FINISHED
Object late 10th century 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: late 10th century | Statement: [church at Brattahlid, timeDepthRepresented, late 10th century]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: timeDepthRepresented
Context triple: [church at Brattahlid, timeDepthRepresented, late 10th century]
  • A. hasTimeDepth chosen
    Indicates that something possesses or spans a measurable extent of time, such as duration, historical depth, or temporal layering.
  • B. testDepth
    Indicates that an entity is evaluated or measured based on how deep or thorough it is, often in terms of levels, layers, or extent below a surface or baseline.
  • C. timeDepthOfLandUse
    Indicates the duration or historical depth over which a particular land use has been present or practiced in a given area.
  • D. reachedDepth
    Indicates that an entity has arrived at or attained a specified depth level in some medium or context.
  • E. hasTemporalResolution
    Indicates that one entity specifies the level of temporal detail or granularity at which another entity’s data, observation, or process is measured or represented.
  • 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_69d806b886bc8190b676e7768b8e01c5 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dba0d3a40081909ba49556130ad0e7 completed April 12, 2026, 1:40 p.m.
PD Predicate disambiguation batch_69d9a03189908190a784a2755f8d81e1 completed April 11, 2026, 1:13 a.m.
Created at: April 9, 2026, 9:34 p.m.