Triple
T31143060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fitzpatrick lordship |
E793841
|
entity |
| Predicate | primarySurname |
P25775
|
FINISHED |
| Object | Fitzpatrick |
E224680
|
NE 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: Fitzpatrick | Statement: [Fitzpatrick lordship, primarySurname, Fitzpatrick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySurname Context triple: [Fitzpatrick lordship, primarySurname, Fitzpatrick]
-
A.
primaryName
chosen
Indicates that the associated name is the main or most commonly used name for the entity in question.
-
B.
firstSurnameListed
Indicates that the referenced surname is the first one appearing in an ordered list of surnames associated with an entity.
-
C.
fatherSurname
Indicates that one entity has the same surname as, or is identified by, the family name of, the father in relation to another entity.
-
D.
motherSurname
Indicates that one entity is the family name or surname of another entity’s mother.
-
E.
usedSurnameFor
Indicates that one entity adopted or employed another entity’s surname as the name by which they were known or referred to.
- F. None of above.
Provenance (4 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b1436f8c481909661087c78aa0abf |
completed | June 11, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:06 p.m.