Triple
T12777588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ambrosio |
E305416
|
entity |
| Predicate | statusInMonastery |
P37071
|
FINISHED |
| Object | revered preacher |
—
|
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: revered preacher | Statement: [Ambrosio, statusInMonastery, revered preacher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInMonastery Context triple: [Ambrosio, statusInMonastery, revered preacher]
-
A.
roleInMonasticism
chosen
Indicates the specific function, position, or status an entity holds within a monastic community or tradition.
-
B.
wasMonkOf
Indicates that a person was a member or monk belonging to a particular religious order, monastery, or monastic community.
-
C.
monasticRequirement
Indicates that one entity imposes, specifies, or embodies a rule, obligation, or condition that must be fulfilled within a monastic or religious order.
-
D.
dissolvedAsMonastery
Indicates that an institution ceased to function as a monastery, typically through formal dissolution or suppression of its monastic status.
-
E.
monastery
Indicates that an entity is or functions as a monastery, typically a religious community or building where monastics live and practice.
- 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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e595e008190b42dff3012d17d66 |
completed | April 10, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:29 p.m.