Triple
T6545675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isabella, Countess of Fife |
E151000
|
entity |
| Predicate | holdsTitleInHerOwnRight |
P63227
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Isabella, Countess of Fife, holdsTitleInHerOwnRight, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holdsTitleInHerOwnRight Context triple: [Isabella, Countess of Fife, holdsTitleInHerOwnRight, yes]
-
A.
heldTitleInHerOwnRight
chosen
Indicates that a woman personally possessed and exercised a title or rank independently, rather than deriving it through a spouse or male relative.
-
B.
hasTitleInLaw
Indicates that an entity holds or is designated by a specific formal title as defined or recognized in law.
-
C.
heldTitleUntil
Indicates that an entity possessed or held a specific title or position continuously up to a particular end date or point in time.
-
D.
titleHolderHouse
Indicates that a particular house or noble family holds or is associated with a specific title.
-
E.
heldTitleByRightOfMother
Indicates that an individual holds a title or rank derived through their mother’s hereditary rights or lineage.
- 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_69c687f3fd60819083bfa583e5bcfa71 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce07332481909a5a7964282eb776 |
completed | March 27, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69c6acf3e3708190b052ec774e607cb7 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:50 p.m.