Triple
T15001850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anand Karaj |
E374109
|
entity |
| Predicate | maritalBondType |
P56596
|
FINISHED |
| Object | monogamous union |
—
|
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: monogamous union | Statement: [Anand Karaj, maritalBondType, monogamous union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritalBondType Context triple: [Anand Karaj, maritalBondType, monogamous union]
-
A.
marriageType
Indicates the specific legal or social category of a marriage relationship that exists between two spouses.
-
B.
hasMaritalRelationshipType
chosen
Indicates the specific type or nature of the marital relationship that exists between two entities.
-
C.
maritalBasis
Indicates that the relationship or status in question is founded on, justified by, or determined due to a marital relationship between the involved entities.
-
D.
spouseType
Indicates the specific role or category of a person within a spousal relationship (e.g., husband, wife, partner).
-
E.
maritalRelations
Indicates a legally or socially recognized spousal relationship or marriage-based connection 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded72fec948190b1c9705538c57976 |
completed | April 15, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:54 a.m.