Triple
T31420395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grabeskirche |
E801514
|
entity |
| Predicate | hatAnderenNamen |
P171853
|
FINISHED |
| Object | Kirche vom Heiligen Grab |
—
|
NE NERFINISHED |
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: Kirche vom Heiligen Grab | Statement: [Grabeskirche, hatAnderenNamen, Kirche vom Heiligen Grab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hatAnderenNamen Context triple: [Grabeskirche, hatAnderenNamen, Kirche vom Heiligen Grab]
-
A.
nameInAfrikaans
Indicates that one entity is the name or designation of another entity when expressed in the Afrikaans language.
-
B.
hasNameInDutch
Indicates that an entity is associated with a specific name or label expressed in the Dutch language.
-
C.
namesAs
Indicates that one entity assigns or uses a particular name or label to refer to another entity.
-
D.
namedAccordingTo
Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
-
E.
hasLaterDutchName
Indicates that an entity was known by a different Dutch name at a later time than its original or earlier Dutch name.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f6a5f656ec81909e02b0b873303adf |
completed | May 3, 2026, 1:33 a.m. |
Created at: April 30, 2026, 8:47 p.m.