Triple
T23459032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earls of Fife |
E568014
|
entity |
| Predicate | notableFemaleHolder |
P82686
|
FINISHED |
| Object | Isabella, Countess of Fife |
—
|
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: Isabella, Countess of Fife | Statement: [Earls of Fife, notableFemaleHolder, Isabella, Countess of Fife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFemaleHolder Context triple: [Earls of Fife, notableFemaleHolder, Isabella, Countess of Fife]
-
A.
notableFemaleWinner
Indicates that the subject is a female who has achieved a notable or distinguished victory in the specified context.
-
B.
notableFemaleMember
chosen
Indicates that an entity has a female member who is particularly prominent, distinguished, or noteworthy within that entity.
-
C.
notableFemaleLegendRanked
Indicates that a female legendary figure is assigned a specific rank or position on a notable legends list or hierarchy.
-
D.
firstWomenAwarded
Indicates that the subject is the first woman to have received the specified award.
-
E.
namedPersonNotableFor
Indicates that a person is especially known or recognized for a particular work, role, achievement, or characteristic.
- 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_69e2458b4c888190b1d7998f9862a558 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a699c0088190a84d7a495a3e3d61 |
completed | April 29, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:53 p.m.