Triple
T33172100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyman, New Hampshire |
E849060
|
entity |
| Predicate | isInStateLegislativeChamber |
P72477
|
FINISHED |
| Object | New Hampshire General Court |
—
|
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: New Hampshire General Court | Statement: [Lyman, New Hampshire, isInStateLegislativeChamber, New Hampshire General Court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInStateLegislativeChamber Context triple: [Lyman, New Hampshire, isInStateLegislativeChamber, New Hampshire General Court]
-
A.
isInStateLegislativeBody
Indicates that an entity serves as a member of a state-level legislative body or assembly.
-
B.
inStateLegislature
chosen
Indicates that an individual holds a position as a member of a state-level legislative body.
-
C.
isPartOfStateLegislature
Indicates that an entity serves as a member or component within a specific state-level legislative body.
-
D.
isInLegislativeAssembly
Indicates that an entity serves as a member or participant within a specific legislative assembly or parliamentary body.
-
E.
hasNationalCongressSeat
Indicates that an entity holds a seat or position in a national congress or equivalent legislative body.
- 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_69f3495be8808190bbf427733df08aad |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:29 a.m.