Triple
T26510973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ellis Grey |
E669680
|
entity |
| Predicate | hasMaidenNameStatus |
P143711
|
FINISHED |
| Object | keeps surname Grey after marriage |
—
|
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: keeps surname Grey after marriage | Statement: [Ellis Grey, hasMaidenNameStatus, keeps surname Grey after marriage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaidenNameStatus Context triple: [Ellis Grey, hasMaidenNameStatus, keeps surname Grey after marriage]
-
A.
maidenNameOf
Indicates that one person’s original family surname before marriage is the maiden name of another person.
-
B.
maidenFamilyStatus
chosen
Indicates the family-related status or condition associated with a person in their maiden (pre-marriage) state.
-
C.
hasMarriedSurname
Indicates that a person’s current surname is the one they adopted through marriage.
-
D.
hasMaritalStatusAtEnd
Indicates that an entity possesses a specific marital status at the end of a given period, event, or reference time.
-
E.
hasCivilStatus
Indicates the civil or marital status that applies to a person or entity (e.g., single, married, divorced).
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: April 27, 2026, 1:20 a.m.