Triple
T1944058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlotte Lee, Countess of Lichfield |
E42021
|
entity |
| Predicate | titleAcquiredBy |
P34204
|
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: [Charlotte Lee, Countess of Lichfield, titleAcquiredBy, marriage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleAcquiredBy Context triple: [Charlotte Lee, Countess of Lichfield, titleAcquiredBy, marriage]
-
A.
titleHeldIn
Indicates that a particular title or position is held within a specified organization, jurisdiction, or contextual domain.
-
B.
titleHolderIsUsually
Indicates that an entity serving as a title holder is typically or most commonly a particular type or category of entity.
-
C.
winnerTitle
Indicates the formal title or designation awarded to the entity that wins a particular competition, contest, or event.
-
D.
laterTitleHolder
Indicates that one entity is a subsequent holder of a particular title or position previously held by another entity.
-
E.
titleHolderTo
Indicates that one entity currently holds or possesses an official title, position, or designation in relation to 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_69a8870e08fc8190a319cbf2600db15f |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb32ebae881908f7541301f0198ae |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abaff25a588190bb4cbc8df9fc6d64 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb32a8d548190a231c7c2ce276a5e |
completed | March 7, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:36 p.m.