Triple
T29693028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen of Georgia |
E751263
|
entity |
| Predicate | typicalMarriagePartner |
P184234
|
FINISHED |
| Object | King of Georgia |
E763949
|
NE 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: King of Georgia | Statement: [Queen of Georgia, typicalMarriagePartner, King of Georgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMarriagePartner Context triple: [Queen of Georgia, typicalMarriagePartner, King of Georgia]
-
A.
isUsuallyMarriedTo
chosen
Indicates that one entity is typically or customarily married to another entity under normal or common circumstances.
-
B.
marriagePartnerIsOlder
Indicates that, within a marriage relationship, the partner being referred to is older in age than the other spouse.
-
C.
partnerInMarriageDuring
Indicates that two entities are spouses of each other during a specified time period.
-
D.
marriesFor
Indicates that one entity enters into marriage with another entity specifically for a particular reason, motive, or benefit.
-
E.
unmarriedPartner
Indicates a relationship where one person is a romantic or domestic partner of another, and they are not legally married to each other.
- F. None of above.
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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a0226c8b2f881909de3c1a5ba40fc49 |
completed | May 11, 2026, 6:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a26f1ad976c819085a59a20b650a1f6 |
completed | June 8, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_6a0225602acc8190978ab4aacc615b8d |
completed | May 11, 2026, 6:52 p.m. |
Created at: April 28, 2026, 7:18 p.m.