Triple
T20291272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubbard Township, Trumbull County, Ohio |
E510027
|
entity |
| Predicate | governingBodyTermLength |
P540
|
FINISHED |
| Object | 4 years |
—
|
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: 4 years | Statement: [Hubbard Township, Trumbull County, Ohio, governingBodyTermLength, 4 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingBodyTermLength Context triple: [Hubbard Township, Trumbull County, Ohio, governingBodyTermLength, 4 years]
-
A.
electsTermLength
Indicates the length of time for which an entity is elected to hold a particular position or office.
-
B.
termLength
chosen
Indicates the duration or period of time for which an agreement, position, or condition remains in effect.
-
C.
numberOfTermInOffice
Indicates the specific ordinal count of how many terms an entity has served in a particular office or position.
-
D.
formedGovernmentTerm
Indicates that an entity established or initiated a specific term or period of governance for a government.
-
E.
headOfStateTermLength
Indicates the duration of time that a person serves in the role of head of state for a given political 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_69e0b4c652388190b782cad965e5a098 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67700c024819091205f5b0a8648e3 |
completed | April 20, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:12 a.m.