Triple
T24840267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bosnian Church |
E621594
|
entity |
| Predicate | modernReinterpretation |
P41953
|
FINISHED |
| Object | indigenous Bosnian Christian church |
—
|
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: indigenous Bosnian Christian church | Statement: [Bosnian Church, modernReinterpretation, indigenous Bosnian Christian church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernReinterpretation Context triple: [Bosnian Church, modernReinterpretation, indigenous Bosnian Christian church]
-
A.
modernInterpretation
chosen
Indicates that one entity is a contemporary or updated interpretation, reading, or understanding of another entity.
-
B.
modernRevivalIn
Indicates that something has experienced a renewed or modern resurgence, popularity, or reinterpretation within a specified place, context, or period.
-
C.
modernUse
Indicates how something is currently used or applied in modern times.
-
D.
modernVariation
Indicates that one entity is a contemporary or updated version, adaptation, or reinterpretation of another.
-
E.
modernEquivalent
Indicates that one entity serves as the contemporary or updated counterpart of another earlier or traditional entity.
- 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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 5:18 a.m.