Triple
T13422616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lieutenant Governor |
E313393
|
entity |
| Predicate | doesNotExistIn |
P1817
|
FINISHED |
| Object | a few U.S. states |
—
|
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: a few U.S. states | Statement: [Lieutenant Governor, doesNotExistIn, a few U.S. states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotExistIn Context triple: [Lieutenant Governor, doesNotExistIn, a few U.S. states]
-
A.
doesNotHave
chosen
Indicates that one entity lacks, is missing, or is not in possession of another entity or attribute.
-
B.
existsFor
Indicates that something is present, available, or holds true for a particular entity, context, or condition.
-
C.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
D.
existsOnlyAs
Indicates that the subject exists solely in a particular form, state, or context specified by the object, and not in any other.
-
E.
existsIf
Indicates that the existence or validity of one entity or condition depends on the presence or truth of another specified condition.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaecf13748190ae40c7b95164f914 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:39 p.m.