Triple
T33030469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Monte Vergine |
E845148
|
entity |
| Predicate | isMendicantOrder |
P58096
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Order of Monte Vergine, isMendicantOrder, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMendicantOrder Context triple: [Order of Monte Vergine, isMendicantOrder, false]
-
A.
dominantMendicantOrders
Indicates that the specified mendicant orders hold a leading or most influential position within a given religious or historical context.
-
B.
monasteryOrder
Indicates that a monastery belongs to, follows, or is affiliated with a particular religious order.
-
C.
mendicantPractice
chosen
Indicates that an entity engages in the practice of begging or living by alms as a religious or spiritual discipline.
-
D.
religiousOrderCode
Indicates the specific religious order or denomination with which an entity is affiliated, represented by a standardized code.
-
E.
religiousOrderSupported
Indicates that one entity provides support—such as resources, endorsement, or maintenance—to 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:24 a.m.