Triple
T27336272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kettlersville, Ohio |
E689958
|
entity |
| Predicate | hasStateLawSystem |
P187565
|
FINISHED |
| Object | Ohio law |
—
|
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: Ohio law | Statement: [Kettlersville, Ohio, hasStateLawSystem, Ohio law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStateLawSystem Context triple: [Kettlersville, Ohio, hasStateLawSystem, Ohio law]
-
A.
hasExtendedLawSystem
Indicates that an entity possesses a comprehensive, detailed, and well-developed system of laws or legal regulations.
-
B.
stateOfLaw
Indicates that a specified legal condition, rule, or status is currently in force or applicable within a given jurisdiction or context.
-
C.
stateLawOf
Indicates that one entity is a law or legal provision that is in force within, or specifically governs, a particular state or subnational jurisdiction.
-
D.
countryOfLegalSystem
Indicates the relationship between a legal system and the country in which that legal system is officially established or applied.
-
E.
hasStateCourt
Indicates that a given jurisdiction or region possesses an official court that operates at the state level.
- 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_69ef355e5b388190a8fc1eba9b4a6656 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb6fdab95c81909acff3c6a2359787 |
completed | May 6, 2026, 4:44 p.m. |
Created at: April 27, 2026, 11:40 a.m.