Triple
T31420407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grabeskirche |
E801514
|
entity |
| Predicate | istBedeutendFür |
P1887
|
FINISHED |
| Object | Christentum |
—
|
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: Christentum | Statement: [Grabeskirche, istBedeutendFür, Christentum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: istBedeutendFür Context triple: [Grabeskirche, istBedeutendFür, Christentum]
-
A.
isImportantFor
chosen
Indicates that something holds significant value, relevance, or necessity in relation to something else.
-
B.
hasParticularSignificanceFor
Indicates that something holds a special, notable, or contextually important relevance or impact for a particular entity or situation.
-
C.
significantSince
Indicates that a relationship, condition, or status has held particular importance or relevance starting from a specified point in time.
-
D.
isMostImportant
Indicates that the referenced entity holds the highest level of importance or priority among a set of entities.
-
E.
significantPort
Indicates that a port holds major importance in terms of trade, transportation, or strategic relevance within a given context.
- 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_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 8:47 p.m.