Triple
T22354363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simon |
E552612
|
entity |
| Predicate | marriageTypeWithWei-Wei |
P8399
|
FINISHED |
| Object | sham marriage |
—
|
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: sham marriage | Statement: [Simon, marriageTypeWithWei-Wei, sham marriage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageTypeWithWei-Wei Context triple: [Simon, marriageTypeWithWei-Wei, sham marriage]
-
A.
marriageType
chosen
Indicates the specific legal or social category of a marriage relationship that exists between two spouses.
-
B.
marriageResolvedBy
Indicates that a marital relationship between two parties has been formally concluded or dissolved through a specific resolving action or process (e.g., divorce, annulment).
-
C.
marriagePattern
Indicates the typical form or structure of a marriage relationship, such as how partners are selected, organized, or related within a social or cultural system.
-
D.
marriageAllianceWith
Indicates a formal marital union established between two parties to create or strengthen a political, social, or strategic alliance.
-
E.
marriesFor
Indicates that one entity enters into marriage with another entity specifically for a particular reason, motive, or benefit.
- 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_69e11e4a0ad08190a385b4d343cf6524 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157ceb2308190941f6507e605a612 |
completed | April 29, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:44 p.m.