Triple
T14881288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suzanne Simonin |
E350004
|
entity |
| Predicate | religiousOrderStatus |
P111626
|
FINISHED |
| Object | forced nun |
—
|
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: forced nun | Statement: [Suzanne Simonin, religiousOrderStatus, forced nun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousOrderStatus Context triple: [Suzanne Simonin, religiousOrderStatus, forced nun]
-
A.
religiousOrderSupported
Indicates that one entity provides support—such as resources, endorsement, or maintenance—to a particular religious order.
-
B.
religiousOrderCode
Indicates the specific religious order or denomination with which an entity is affiliated, represented by a standardized code.
-
C.
religiousOrderOrRole
chosen
Indicates that an entity has a specific religious affiliation, order, or role within a religious tradition.
-
D.
religiousOrderAssociation
Indicates that an entity is formally connected to, affiliated with, or a member of a particular religious order.
-
E.
religiousOrderSucceededBy
Indicates that one religious order is replaced or followed by another as its successor in a historical or organizational sequence.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5e7c0e48190af2d68a71130585c |
completed | April 15, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:55 a.m.