Triple
T30970644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OFMCap |
E789086
|
entity |
| Predicate | usedAsPostnominalLettersBy |
P136120
|
FINISHED |
| Object | Capuchin friars |
—
|
NE NERFINISHED |
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: Capuchin friars | Statement: [OFMCap, usedAsPostnominalLettersBy, Capuchin friars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsPostnominalLettersBy Context triple: [OFMCap, usedAsPostnominalLettersBy, Capuchin friars]
-
A.
hasPostnominalLetters
Indicates that a person holds specific postnominal letters (abbreviations after their name) signifying qualifications, honors, or titles.
-
B.
equivalentEnglishPostNominal
Indicates that two post-nominal modifiers in English (elements following a noun) express the same meaning or function and can be treated as equivalent.
-
C.
usesPostNominalsIn
chosen
Indicates that an entity customarily appends specific post-nominal letters to its name within a given context or jurisdiction.
-
D.
equivalentFrenchPostNominal
Indicates that one entity has a corresponding or matching French post-nominal form equivalent to that of another entity.
-
E.
usedAsFirstNameOf
Indicates that one entity functions as the given or first name of another entity.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: April 29, 2026, 8:54 p.m.