Triple
T23288760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia Young |
E589966
|
entity |
| Predicate | personalStatus |
P20884
|
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: [Georgia Young, personalStatus, divorced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: personalStatus Context triple: [Georgia Young, personalStatus, divorced]
-
A.
marital status
chosen
Indicates the legal or social state of a person’s marriage-related relationship, such as being single, married, divorced, or widowed.
-
B.
possibleSocialStatus
Indicates that one entity may hold, attain, or be associated with a particular social status in relation to another context or system.
-
C.
civicStatus
Indicates the legal or social standing of an individual within a civic or societal framework, such as marital or citizenship status.
-
D.
lifeStatus
Indicates the current state of an entity’s existence, such as whether it is alive, dead, or in another defined life condition.
-
E.
spouseStatus
Indicates the marital relationship status between two individuals, such as whether they are currently spouses, formerly spouses, or not 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_69e25d1af9d88190a0b9b5e8fa608618 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19649570c8190b565fafa55b1f886 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5:01 p.m.