Triple
T1340355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia House of Representatives |
E28448
|
entity |
| Predicate | membersTitle |
P1648
|
FINISHED |
| Object | state representative |
—
|
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: state representative | Statement: [Georgia House of Representatives, membersTitle, state representative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: membersTitle Context triple: [Georgia House of Representatives, membersTitle, state representative]
-
A.
memberTitle
chosen
Indicates the formal title or designation held by a member within a group, organization, or body.
-
B.
memberEntities
Indicates that certain entities belong to, or are included as members within, a larger group or collection.
-
C.
boardMember
Indicates that a person serves on the governing board of an organization, participating in its oversight and decision-making.
-
D.
typicalMembers
Indicates that the related entities are representative or characteristic members of a larger group, category, or class.
-
E.
boardMembersRepresent
Indicates that designated board members act on behalf of, and in the interests of, a particular organization or group.
- 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c21490488190b4281a16c87677d1 |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef3e8fc8190ac9a1ba9b5879483 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.