Triple
T21841925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiki |
E539274
|
entity |
| Predicate | spouseCharacterTrait |
P91240
|
FINISHED |
| Object | controlling husband |
—
|
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: controlling husband | Statement: [Kiki, spouseCharacterTrait, controlling husband]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseCharacterTrait Context triple: [Kiki, spouseCharacterTrait, controlling husband]
-
A.
spouseCharacteristic
chosen
Indicates that a particular characteristic, trait, or attribute is associated with a person’s spouse within the relationship.
-
B.
spouseCharacterization
Indicates how one spouse describes, evaluates, or characterizes the other spouse within their relationship.
-
C.
spouseCharacterOf
Indicates a marital relationship where one character is the spouse of another character.
-
D.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
E.
spouse
Indicates that two entities are married to each other in a legally or socially recognized partnership.
- 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_69e0c476c3c88190a92d08ebb59a128a |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0a7acb17c81908c0de0afac5a9fa7 |
completed | April 28, 2026, 12:27 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.