Triple
T8106446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poor Clares |
E189237
|
entity |
| Predicate | hasSuperiorTitle |
P23605
|
FINISHED |
| Object | abbess |
—
|
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: abbess | Statement: [Poor Clares, hasSuperiorTitle, abbess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuperiorTitle Context triple: [Poor Clares, hasSuperiorTitle, abbess]
-
A.
hasAncestralTitle
Indicates that an entity holds or is associated with a hereditary or historically inherited title passed down through ancestry.
-
B.
hasRepresentativeTitle
Indicates that an entity holds a formal title or designation that serves as its primary or most commonly used label or name.
-
C.
hasPatronalTitle
Indicates that an entity holds or is associated with a specific patronal or honorific title, typically reflecting patronage, protection, or dedication.
-
D.
isSeniorTitle
Indicates that one title holds a higher or more senior rank or status relative to another title.
-
E.
higherTitleOf
chosen
Indicates that one entity holds a job or position title that is hierarchically superior to the title held by 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_69ca82b9d5848190a24672775d5c5011 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb42f735c8819090d0d822644c0a51 |
completed | March 31, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69cb04a2ed1c8190b73562321ad688bc |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:31 p.m.