Triple
T33030096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guillaume d’Orange |
E845140
|
entity |
| Predicate | religionInTexts |
P39124
|
FINISHED |
| Object | Christianity |
—
|
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: Christianity | Statement: [Guillaume d’Orange, religionInTexts, Christianity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religionInTexts Context triple: [Guillaume d’Orange, religionInTexts, Christianity]
-
A.
associatedReligionInTexts
chosen
Indicates that a particular religion is mentioned or linked in written texts in connection with the given entity.
-
B.
religiousTextMentionedIn
Indicates that a religious text is referenced, cited, or discussed within another work or source.
-
C.
religiousTextOf
Indicates that one entity is a religious text that is sacred to, foundational for, or primarily associated with another entity (such as a religion, denomination, or faith community).
-
D.
religiousTextType
Indicates that one entity is a religious text and specifies the type or category of that religious text in relation to the other entity.
-
E.
religiousTextCategory
Indicates that a religious text belongs to or is classified under a particular category or type.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff14d596e88190be5263b7f96a96cd |
completed | May 9, 2026, 11:04 a.m. |
| PD | Predicate disambiguation | batch_69ff13f0208081909369aeb3b77a6b1f |
completed | May 9, 2026, 11:01 a.m. |
Created at: May 1, 2026, 1:24 a.m.