Triple
T28326264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peel County |
E717416
|
entity |
| Predicate | effectiveDateOfOrganization |
P83226
|
FINISHED |
| Object | 1853 |
—
|
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: 1853 | Statement: [Peel County, effectiveDateOfOrganization, 1853]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectiveDateOfOrganization Context triple: [Peel County, effectiveDateOfOrganization, 1853]
-
A.
effectivePeriodStart
chosen
Indicates the date and time when a specified condition, status, or agreement becomes valid or goes into effect.
-
B.
complianceDate
Indicates the date on which an entity meets, satisfies, or becomes compliant with a specified requirement, rule, or standard.
-
C.
lessEffectiveAt
Indicates that one entity has a reduced ability or lower level of success in performing, influencing, or achieving a particular action or outcome compared to another.
-
D.
complianceDateForMostCoveredEntities
Indicates the date by which the majority of entities subject to a given rule or requirement must achieve compliance.
-
E.
effectiveFor
Indicates that one entity successfully produces the intended effect, benefit, or desired outcome for another entity or condition.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 28, 2026, 12:28 a.m.