Triple
T31420413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grabeskirche |
E801514
|
entity |
| Predicate | wirdMitgenutztVon |
P171854
|
FINISHED |
| Object | Syrisch-orthodoxe Kirche |
—
|
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: Syrisch-orthodoxe Kirche | Statement: [Grabeskirche, wirdMitgenutztVon, Syrisch-orthodoxe Kirche]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wirdMitgenutztVon Context triple: [Grabeskirche, wirdMitgenutztVon, Syrisch-orthodoxe Kirche]
-
A.
areUsedBy
Indicates that certain entities serve as tools, resources, or means that are utilized or employed by other entities.
-
B.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
C.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
D.
notablyUsedWith
Indicates that one entity is commonly or prominently used together with another entity, in a way that is especially characteristic or noteworthy.
-
E.
isFamouslyUsedIn
Indicates that something is widely recognized or well-known for being used in a particular context, work, or situation.
- 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.