Triple
T36178802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claudia Joy Holden |
E1046648
|
entity |
| Predicate | spouseRankAssociation |
P37264
|
FINISHED |
| Object | general's wife |
—
|
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: general's wife | Statement: [Claudia Joy Holden, spouseRankAssociation, general's wife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseRankAssociation Context triple: [Claudia Joy Holden, spouseRankAssociation, general's wife]
-
A.
marriedToRank
chosen
Indicates that one entity is married to another entity who holds a specific rank or position.
-
B.
spouseType
Indicates the specific role or category of a person within a spousal relationship (e.g., husband, wife, partner).
-
C.
spouseRelationshipContext
Indicates a marital relationship context between two entities, specifying that they are spouses or partners in a recognized marriage-like union.
-
D.
spouseMemberOf
Indicates that a person’s spouse is a member of a specified group, organization, or entity.
-
E.
relationshipToSpouse
Indicates the specific familial or social role one person holds in relation to their spouse (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_69f76e3c1b10819081fc7a807a71cf84 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
Created at: May 3, 2026, 4:08 p.m.