Triple
T24356901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Margery Spencer |
E613946
|
entity |
| Predicate | nobleTitleByMarriage |
P135257
|
FINISHED |
| Object | Viscountess Greenwood |
—
|
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: Viscountess Greenwood | Statement: [Margery Spencer, nobleTitleByMarriage, Viscountess Greenwood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleTitleByMarriage Context triple: [Margery Spencer, nobleTitleByMarriage, Viscountess Greenwood]
-
A.
aristocraticTitleByMarriage
chosen
Indicates that an individual holds an aristocratic title acquired through marriage rather than by birth or independent grant.
-
B.
aristocraticTitleBeforeMarriage
Indicates that the subject held a specific aristocratic title prior to entering into marriage.
-
C.
spouseNameAfterEnnoblement
Indicates that the predicate specifies the spouse’s name as it is used after the spouse has been ennobled or granted a noble title.
-
D.
marriageThroughWhichTitleHeld
Indicates that a noble or formal title is held by a person specifically by virtue of (i.e., as a result of) a particular marriage.
-
E.
nobleTitleElevated
Indicates that an entity’s noble rank or title has been raised to a higher level of nobility.
- 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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29349ee188190a9d54b2c725b8a27 |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2 a.m.