Triple
T6583981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Albani Church, Göttingen |
E157373
|
entity |
| Predicate | relativeAgeInCity |
P43008
|
FINISHED |
| Object | one of the oldest churches in Göttingen |
—
|
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: one of the oldest churches in Göttingen | Statement: [St. Albani Church, Göttingen, relativeAgeInCity, one of the oldest churches in Göttingen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeAgeInCity Context triple: [St. Albani Church, Göttingen, relativeAgeInCity, one of the oldest churches in Göttingen]
-
A.
hasRelativeAge
chosen
Indicates that one entity has an age that is defined or compared in relation to the age of another entity.
-
B.
homeCitySince
Indicates the city that has served as an entity’s home starting from a specified point in time.
-
C.
residesNear
Indicates that one entity lives or is located in close physical proximity to another entity.
-
D.
timeRelativeToBirth
Indicates the temporal position of an event or state relative to an entity’s birth (e.g., before, at, or after birth).
-
E.
urbanStatusSince
Indicates the point in time since which an entity has held an urban status or classification.
- 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_69c6882b3a108190b3a9eb343ae4162c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c07cdf048190945ca5810fb1de88 |
completed | March 27, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c6acfb462481909cb7aff5af4bca9d |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:54 p.m.