Triple
T31420430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grabeskirche |
E801514
|
entity |
| Predicate | wurdeErweitertImJahrhundert |
P137470
|
FINISHED |
| Object | 12. Jahrhundert |
—
|
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: 12. Jahrhundert | Statement: [Grabeskirche, wurdeErweitertImJahrhundert, 12. Jahrhundert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wurdeErweitertImJahrhundert Context triple: [Grabeskirche, wurdeErweitertImJahrhundert, 12. Jahrhundert]
-
A.
hasLaterAdditionsFromCentury
chosen
Indicates that additional elements or modifications were made to something in a later century than its original creation or primary period.
-
B.
discoveredInCentury
Indicates that an entity was discovered during a specific century.
-
C.
introducedInCentury
Indicates the century during which something (such as an idea, technology, practice, or entity) was first introduced or came into use.
-
D.
acquiredInCentury
Indicates that one entity was acquired during a specific century represented by the other entity.
-
E.
adoptedInCentury
Indicates that something (such as a practice, idea, or object) was first adopted or came into use during a specified century.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 30, 2026, 8:47 p.m.