Triple
T10836441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yun Chi Chung |
E255769
|
entity |
| Predicate | marriageStatusWithReddFoxx |
P5173
|
FINISHED |
| Object | divorced |
—
|
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: divorced | Statement: [Yun Chi Chung, marriageStatusWithReddFoxx, divorced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageStatusWithReddFoxx Context triple: [Yun Chi Chung, marriageStatusWithReddFoxx, divorced]
-
A.
parentsMarriageStatus
Indicates the marital status relationship between an individual’s parents (e.g., married, divorced, separated, never married).
-
B.
spouseStatus
chosen
Indicates the marital relationship status between two individuals, such as whether they are currently spouses, formerly spouses, or not married to each other.
-
C.
marital status
Indicates the legal or social state of a person’s marriage-related relationship, such as being single, married, divorced, or widowed.
-
D.
spouseStatusAtMarriage
Indicates the marital status each partner held at the time their marriage to one another was formed.
-
E.
hasMarriage
Indicates a marital relationship exists between the two entities, specifying that they are or were legally married to each other.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d746ff70148190b844ab92d796af6c |
completed | April 9, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69d70d25280c8190b648d7d1958b413a |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.