Triple
T17562663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercredi Saint |
E427730
|
entity |
| Predicate | liéÀÉvénementBiblique |
P36136
|
FINISHED |
| Object | derniers jours de Jésus à Jérusalem |
—
|
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: derniers jours de Jésus à Jérusalem | Statement: [Mercredi Saint, liéÀÉvénementBiblique, derniers jours de Jésus à Jérusalem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liéÀÉvénementBiblique Context triple: [Mercredi Saint, liéÀÉvénementBiblique, derniers jours de Jésus à Jérusalem]
-
A.
scripturalEvent
Indicates that an event is described, referenced, or established within a scriptural or sacred text.
-
B.
associatedBiblicalEvent
chosen
Indicates that there is a connection or linkage between an entity and a specific event described in the Bible.
-
C.
scriptureFor
Indicates that one entity serves as a scriptural or authoritative religious text for another entity (such as a person, group, or belief system).
-
D.
scriptureFocus
Indicates that something centers on, emphasizes, or is primarily concerned with religious scripture or sacred texts.
-
E.
religiousEvent
Indicates that an event is related to religious practices, observances, or ceremonies.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e456285c808190953a49e77366d8bd |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fd7d048190b54ee4c6155612a5 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.