Triple
T30644566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohio's congressional delegation |
E780084
|
entity |
| Predicate | statehoodDateOfOhio |
P11034
|
FINISHED |
| Object | 1803 |
—
|
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: 1803 | Statement: [Ohio's congressional delegation, statehoodDateOfOhio, 1803]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statehoodDateOfOhio Context triple: [Ohio's congressional delegation, statehoodDateOfOhio, 1803]
-
A.
statehoodYear
chosen
Indicates the year in which an entity officially became a recognized state or attained statehood status.
-
B.
startTimeOfRole_capital of Ohio
Indicates the point in time when an entity began serving in the role of capital of Ohio.
-
C.
statehoodEvent
Indicates an event or process through which an entity attains, changes, or loses the status of being a recognized state.
-
D.
termStartAsOhioSecretaryOfState
Indicates the date or point in time when an individual begins serving in the role of Ohio Secretary of State.
-
E.
stateFounded
Indicates that a particular state was established or created at a specific time or by a specific founding event or agent.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: April 29, 2026, 8:29 p.m.