Triple
T24022236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onggirat |
E594853
|
entity |
| Predicate | providedBridesTo |
P1261
|
FINISHED |
| Object | Genghis Khan’s lineage |
—
|
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: Genghis Khan’s lineage | Statement: [Onggirat, providedBridesTo, Genghis Khan’s lineage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providedBridesTo Context triple: [Onggirat, providedBridesTo, Genghis Khan’s lineage]
-
A.
bride
Indicates that an entity is a woman who is getting married or has just been married in relation to a wedding event or spouse.
-
B.
comparesBrideTo
Indicates that one entity is being evaluated or contrasted against another specifically in the role or context of a bride.
-
C.
associatedWithWeddingOf
Indicates a relationship where something is connected or related to the wedding event of specific individuals.
-
D.
brideFamily
Indicates a familial relationship in which one party is the family or relatives of the bride in a marriage context.
-
E.
providedFor
chosen
Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d7667ff08190bfd14aa4eb776f21 |
completed | April 29, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:51 p.m.