Triple
T5175453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fray Tomás de Berlanga |
E116785
|
entity |
| Predicate | monasticVows |
P40813
|
FINISHED |
| Object | Dominican |
—
|
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: Dominican | Statement: [Fray Tomás de Berlanga, monasticVows, Dominican]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monasticVows Context triple: [Fray Tomás de Berlanga, monasticVows, Dominican]
-
A.
tookReligiousVows
chosen
Indicates that an entity formally committed to a religious life by taking recognized vows within a religious tradition.
-
B.
tookReligiousVowsOn
Indicates that an entity formally committed to religious vows on a specific date or occasion.
-
C.
monasticLife
Indicates a relationship where an entity lives according to monastic rules, practices, and commitments, typically within a religious community.
-
D.
monasticCode
Indicates that an entity follows, is governed by, or is associated with a specific set of monastic rules or disciplinary code.
-
E.
roleInMonasticism
Indicates the specific function, position, or status an entity holds within a monastic community or tradition.
- 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_69bd446140f08190becb93c61158f27f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd797349008190b87ad9d0d3eb667f |
completed | March 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69bd77b529948190b86671ebe43f4734 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:45 p.m.