Triple
T19335436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brownhelm Township |
E483609
|
entity |
| Predicate | trusteeTermLength |
P33746
|
FINISHED |
| Object | four 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: four years | Statement: [Brownhelm Township, trusteeTermLength, four years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trusteeTermLength Context triple: [Brownhelm Township, trusteeTermLength, four years]
-
A.
termLength
Indicates the duration or period of time for which an agreement, position, or condition remains in effect.
-
B.
termLengthCharacteristic
Indicates the specific duration-related property or feature associated with a term (such as its length or time span).
-
C.
termLengthNumber
chosen
Indicates the numerical value representing the duration or length of a specified term.
-
D.
electsTermLength
Indicates the length of time for which an entity is elected to hold a particular position or office.
-
E.
termLengthCondition
Indicates a condition or constraint specifying the required or allowed duration/length of a term (such as a contract, agreement, or period).
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e61644b80c819080f9bca086424a36 |
completed | April 20, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:33 p.m.