Triple
T10673666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ward Hunt |
E251557
|
entity |
| Predicate | servedOnCourtDuring |
P95252
|
FINISHED |
| Object | Reconstruction era |
—
|
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: Reconstruction era | Statement: [Ward Hunt, servedOnCourtDuring, Reconstruction era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedOnCourtDuring Context triple: [Ward Hunt, servedOnCourtDuring, Reconstruction era]
-
A.
servedAtCourtOf
Indicates that an individual performed official duties or held a position in the court of a particular ruler or governing authority.
-
B.
positionInCourt
Indicates the specific role or standing an entity holds within a court setting or judicial proceeding.
-
C.
endOfTermOnCourt
Indicates the point in time when an individual's service or tenure on a court officially concludes.
-
D.
presidedAt
Indicates that one entity held a position of authority or leadership over the proceedings or activities that took place at a specific event or location.
-
E.
usedAsHomeCourtOf
Indicates that a particular venue or location serves as the primary home court where a team or individual regularly hosts its games or matches.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fb9299708190a0a3818f2e4e9bf5 |
completed | April 9, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8a93208190a573061387e2aebb |
completed | April 8, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69d6df47899481909ac0e518d94883cb |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 9:09 p.m.