Triple
T33420491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 20th United States Congress |
E855832
|
entity |
| Predicate | hasNumberOfStatesRepresented |
P14077
|
FINISHED |
| Object | 24 |
—
|
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: 24 | Statement: [20th United States Congress, hasNumberOfStatesRepresented, 24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfStatesRepresented Context triple: [20th United States Congress, hasNumberOfStatesRepresented, 24]
-
A.
numberOfStatesRepresented
chosen
Indicates how many distinct states are represented or covered in a given context or entity.
-
B.
hasNumberOfStatesAndDistricts
Indicates a relationship where an entity is associated with a specific count of its constituent states and districts.
-
C.
hasSingleRepresentativeForState
Indicates that exactly one representative serves or acts on behalf of a given state.
-
D.
memberStatesRepresented
Indicates that certain member states are officially represented or have representation within a given body, context, or arrangement.
-
E.
representsStateIn
Indicates that one entity serves as a representative or embodiment of a particular state, condition, or status of another entity.
- 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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: May 1, 2026, 1:36 a.m.