Triple
T18610107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knight of the Order of St. Gregory the Great |
E454868
|
entity |
| Predicate | wearerMayBe |
P52283
|
FINISHED |
| Object | clergy in rare cases |
—
|
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: clergy in rare cases | Statement: [Knight of the Order of St. Gregory the Great, wearerMayBe, clergy in rare cases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wearerMayBe Context triple: [Knight of the Order of St. Gregory the Great, wearerMayBe, clergy in rare cases]
-
A.
wearerType
chosen
Indicates the type or category of entity that is intended to wear or use the associated item.
-
B.
wearerMust
Indicates that a specified item or object is required to be worn by a particular entity under certain conditions or rules.
-
C.
wearerStatus
Indicates the condition or role of an entity in its capacity as a wearer of something (e.g., clothing, equipment, or an accessory).
-
D.
wearableBy
Indicates that one entity is designed or suitable to be worn on the body by another entity.
-
E.
wearerDevice
Indicates that a device is worn or carried by a particular entity (the wearer).
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54d0048b08190a7dd407f14d95799 |
completed | April 19, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:45 a.m.