Triple
T4496235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lily Bell |
E100701
|
entity |
| Predicate | maritalStatusAtIntroduction |
P20884
|
FINISHED |
| Object | married |
—
|
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: married | Statement: [Lily Bell, maritalStatusAtIntroduction, married]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritalStatusAtIntroduction Context triple: [Lily Bell, maritalStatusAtIntroduction, married]
-
A.
spouseStatusAtMarriage
Indicates the marital status each partner held at the time their marriage to one another was formed.
-
B.
marital status
chosen
Indicates the legal or social state of a person’s marriage-related relationship, such as being single, married, divorced, or widowed.
-
C.
spouseStatus
Indicates the marital relationship status between two individuals, such as whether they are currently spouses, formerly spouses, or not married to each other.
-
D.
marriageType
Indicates the specific legal or social category of a marriage relationship that exists between two spouses.
-
E.
hasMaritalRelationshipType
Indicates the specific type or nature of the marital relationship that exists between two entities.
- 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_69bd43cdf15081909a4fa2585ff63b3e |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd56bf3ff48190b3aae0136d7fce45 |
completed | March 20, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_69bd521671688190bc655d25fa77eba2 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1 p.m.