Triple
T16186979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint John Berchmans |
E392830
|
entity |
| Predicate | enteredReligiousOrder |
P27505
|
FINISHED |
| Object | 1616 |
—
|
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: 1616 | Statement: [Saint John Berchmans, enteredReligiousOrder, 1616]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredReligiousOrder Context triple: [Saint John Berchmans, enteredReligiousOrder, 1616]
-
A.
religiousOrderOrRole
Indicates that an entity has a specific religious affiliation, order, or role within a religious tradition.
-
B.
tookReligiousVowsOn
chosen
Indicates that an entity formally committed to religious vows on a specific date or occasion.
-
C.
tookReligiousVows
Indicates that an entity formally committed to a religious life by taking recognized vows within a religious tradition.
-
D.
religiousOrderSucceededBy
Indicates that one religious order is replaced or followed by another as its successor in a historical or organizational sequence.
-
E.
inspiredReligiousOrder
Indicates that one entity motivated, influenced, or served as a model for the founding or development of a particular religious order.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e22061f47481909ededd5eed40f5a4 |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.