Triple
T18486674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lieutenant Governor of Missouri |
E451708
|
entity |
| Predicate | canHoldOtherEmployment |
P131859
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lieutenant Governor of Missouri, canHoldOtherEmployment, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canHoldOtherEmployment Context triple: [Lieutenant Governor of Missouri, canHoldOtherEmployment, true]
-
A.
eligibleWork
Indicates that a particular work satisfies the necessary conditions or criteria to qualify for a specified status, benefit, or consideration.
-
B.
commonEmployment
Indicates that two or more entities share the same employer or have worked for the same organization.
-
C.
canHire
Indicates that one entity has the authority or ability to employ or recruit another entity.
-
D.
stateOfEmployment
Indicates that one entity’s employment status or condition is defined in relation to another entity (such as an employer, position, or employment situation).
-
E.
mayWorkIn
Indicates that an entity is allowed or has the possibility to work in a particular place, organization, or context.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e531d7e79c819083bf5c54faaa4810 |
completed | April 19, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:35 a.m.