Triple
T31845919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Lady of Tennessee |
E812938
|
entity |
| Predicate | mayBeVacantWhen |
P35080
|
FINISHED |
| Object | governor is unmarried |
—
|
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: governor is unmarried | Statement: [First Lady of Tennessee, mayBeVacantWhen, governor is unmarried]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeVacantWhen Context triple: [First Lady of Tennessee, mayBeVacantWhen, governor is unmarried]
-
A.
canBeVacantWhen
chosen
Indicates the conditions or circumstances under which something is allowed or able to remain unoccupied or empty.
-
B.
canBeVacant
Indicates that an entity (such as a position, property, or role) is capable of being unoccupied or without an assigned holder.
-
C.
canBeVacated
Indicates that a position, status, or decision is capable of being annulled, set aside, or rendered void.
-
D.
vacatedWhen
Indicates the time or date at which something (such as a position, office, or place) was given up, left, or no longer occupied.
-
E.
mayBeReservedBy
Indicates that an entity is eligible or allowed to be reserved by another entity, without asserting that the reservation has actually occurred.
- 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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 30, 2026, 11:50 p.m.