Triple
T14252580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John A. T. Hull |
E353305
|
entity |
| Predicate | numberOfCongressionalTermsServed |
P78246
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [John A. T. Hull, numberOfCongressionalTermsServed, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfCongressionalTermsServed Context triple: [John A. T. Hull, numberOfCongressionalTermsServed, 10]
-
A.
representedInCongressSince
Indicates that an entity has served as a representative in a legislative congress continuously since a specified date or time.
-
B.
numberOfTermInOffice
chosen
Indicates the specific ordinal count of how many terms an entity has served in a particular office or position.
-
C.
servedInCongress
Indicates that an individual held an official legislative position as a member of a national congress during some period of time.
-
D.
positionHeldInLegislature
Indicates that an entity holds or has held a specific official role or seat within a legislative body.
-
E.
legislativeTermNumber
Indicates the ordinal number assigned to a specific legislative term within a sequence of legislative periods.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6297f38c819090d7c7fd8bfa2e9e |
completed | April 14, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69de05c09b7881908acbca18bd7d997c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:08 a.m.