Triple
T30626906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zulu brides |
E779604
|
entity |
| Predicate | maritalStatusAfterEvent |
P107707
|
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: [Zulu brides, maritalStatusAfterEvent, married]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritalStatusAfterEvent Context triple: [Zulu brides, maritalStatusAfterEvent, married]
-
A.
socialStatusAfterMarriage
Indicates the social status an individual holds as a result of, or following, their marriage.
-
B.
marriageStatusChange
Indicates a change in an entity’s marital status from one state to another at a particular point in time.
-
C.
hasMaritalStatusAtEnd
chosen
Indicates that an entity possesses a specific marital status at the end of a given period, event, or reference time.
-
D.
marital status
Indicates the legal or social state of a person’s marriage-related relationship, such as being single, married, divorced, or widowed.
-
E.
hasMaritalStatusAfterFirstMarriage
Indicates that an entity’s marital status at a given time is the one it holds after its first marriage has occurred.
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 8:28 p.m.