Triple
T35416348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loyal, Oklahoma |
E1023650
|
entity |
| Predicate | hasStateLegalSystem |
P187565
|
FINISHED |
| Object | Oklahoma 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: Oklahoma law | Statement: [Loyal, Oklahoma, hasStateLegalSystem, Oklahoma law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStateLegalSystem Context triple: [Loyal, Oklahoma, hasStateLegalSystem, Oklahoma law]
-
A.
hasStateLawSystem
chosen
Indicates that a jurisdiction or entity operates under or is governed by a particular system of state laws.
-
B.
hasLegalSystemType
Indicates that an entity possesses or is governed by a particular type or form of legal system.
-
C.
countryOfLegalSystem
Indicates the relationship between a legal system and the country in which that legal system is officially established or applied.
-
D.
hasExtendedLawSystem
Indicates that an entity possesses a comprehensive, detailed, and well-developed system of laws or legal regulations.
-
E.
usedLegalSystemOf
Indicates that one entity applied, followed, or operated under the legal system or body of laws belonging to another 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_69f76df54bac8190bd0d3b0eb35cda5f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffed8912488190baa05f572e5b1b89 |
completed | May 10, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69ffed12a76c8190ad85c6ac869c72e9 |
completed | May 10, 2026, 2:27 a.m. |
Created at: May 3, 2026, 4:03 p.m.