Triple
T30016679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maccabees |
E762614
|
entity |
| Predicate | universityReligiousIdentity |
P45
|
FINISHED |
| Object | Jewish |
—
|
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: Jewish | Statement: [Maccabees, universityReligiousIdentity, Jewish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: universityReligiousIdentity Context triple: [Maccabees, universityReligiousIdentity, Jewish]
-
A.
religiousCampus
Indicates that a campus is affiliated with, governed by, or primarily dedicated to a particular religion or religious organization.
-
B.
governingReligionOfInstitution
Indicates that a particular religion serves as the official or primary religious affiliation guiding or overseeing an institution.
-
C.
religiousSpectrum
Indicates a relationship that places entities along a range or continuum of religious belief, practice, or affiliation.
-
D.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
E.
religiousAffiliation
chosen
Indicates that one entity has a specified religious association, belief system, or denominational membership.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6798536288190bd0541e060dd9f6a |
completed | May 2, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 6:46 p.m.