Triple
T25157001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karen Wilson |
E626339
|
entity |
| Predicate | hasSpouseGender |
P32629
|
FINISHED |
| Object | female |
—
|
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: female | Statement: [Karen Wilson, hasSpouseGender, female]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpouseGender Context triple: [Karen Wilson, hasSpouseGender, female]
-
A.
spouseGender
chosen
Indicates the gender of a person’s spouse in a marital relationship.
-
B.
hasSpouseUsingFeminineForm
Indicates that one entity has a spouse, and this spousal relationship is expressed or recorded using a feminine grammatical form.
-
C.
spouseOfType
Indicates that one entity is the spouse of another, specifying the type or role of that spousal relationship.
-
D.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
E.
spouseType
Indicates the specific role or category of a person within a spousal relationship (e.g., husband, wife, partner).
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 18, 2026, 6:30 a.m.