Triple
T22700515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sakharam |
E561307
|
entity |
| Predicate | rejectsInstitution |
P149374
|
FINISHED |
| Object | 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: Marriage | Statement: [Sakharam, rejectsInstitution, Marriage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rejectsInstitution Context triple: [Sakharam, rejectsInstitution, Marriage]
-
A.
rejectedIn
Indicates that an entity or proposal was not accepted or was turned down within a specific context, process, or location.
-
B.
rejectedBecause
Indicates that one entity refused, dismissed, or did not accept another entity specifically due to a stated reason or cause.
-
C.
rejectedBy
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
D.
rejectedAt
Indicates the time or date at which something (such as a request, application, or proposal) was formally rejected.
-
E.
rejectedAdvancesOf
Indicates that one entity declined, refused, or did not accept the romantic or sexual advances made by another entity.
- F. None of above. chosen
Provenance (4 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_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178ca683c81909f6b4e26b85c99c1 |
completed | April 29, 2026, 3:19 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:15 p.m.