Triple
T33086824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mortimer dynasty |
E846662
|
entity |
| Predicate | acquiredThroughMarriage |
P4942
|
FINISHED |
| Object | Earldom of Ulster |
—
|
NE NERFINISHED |
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: Earldom of Ulster | Statement: [Mortimer dynasty, acquiredThroughMarriage, Earldom of Ulster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquiredThroughMarriage Context triple: [Mortimer dynasty, acquiredThroughMarriage, Earldom of Ulster]
-
A.
usedDuringMarriageTo
Indicates that something (such as a name, asset, or status) was in use by or applicable to a person or entity specifically during the period of their marriage.
-
B.
propertyOwnedWithSpouse
Indicates that a property is jointly owned by an individual together with their spouse.
-
C.
heldByMarriage
Indicates that two entities are connected through a marital relationship, such that one is held or bound to the other by marriage.
-
D.
marriedInto
chosen
Indicates that one entity became connected to another’s family or group through marriage, rather than by birth or prior membership.
-
E.
takenFromHusbandBy
Indicates that something previously belonging to a husband was removed or seized by another specified party.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:26 a.m.