Triple
T20442642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heddal Stave Church |
E501433
|
entity |
| Predicate | relativeSizeDescription |
P28652
|
FINISHED |
| Object | largest stave church in Norway |
—
|
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: largest stave church in Norway | Statement: [Heddal Stave Church, relativeSizeDescription, largest stave church in Norway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeSizeDescription Context triple: [Heddal Stave Church, relativeSizeDescription, largest stave church in Norway]
-
A.
sizeDescription
chosen
Indicates a relationship where one entity provides descriptive information about the size or scale of another entity.
-
B.
relativeSizeOnTethys
Indicates how the size of one entity compares to another specifically in the context of Tethys.
-
C.
relativeLength
Indicates a comparative relationship between entities based on how long they are relative to one another.
-
D.
relativeSizeInJapan
Indicates how the size of one entity compares to another specifically within the context of Japan.
-
E.
relativeFruitSize
Indicates the comparative size relationship between one fruit and another (e.g., larger than, smaller than, or similar in size).
- 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_69e0b4ac0a1c81908845d0f8a56abce8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e685f3b794819080745b135a305ba7 |
completed | April 20, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:32 a.m.