Triple
T13224637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FL |
E314844
|
entity |
| Predicate | denotesJurisdictionLevel |
P6712
|
FINISHED |
| Object | state |
—
|
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: state | Statement: [FL, denotesJurisdictionLevel, state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denotesJurisdictionLevel Context triple: [FL, denotesJurisdictionLevel, state]
-
A.
jurisdictionLevel
chosen
Indicates the scope or tier of authority under which an entity or action is legally governed or regulated.
-
B.
definedJurisdictionOf
Indicates that one entity formally establishes or specifies the scope, boundaries, or authority of another entity’s jurisdiction.
-
C.
organizationJurisdiction
Indicates the legal or administrative area (such as a country, state, or city) within whose authority an organization operates or is governed.
-
D.
typeOfJurisdiction
Indicates the specific kind or category of legal authority or control that one jurisdiction holds in relation to a given legal or administrative context.
-
E.
governmentJurisdiction
Indicates the governmental body or authority that has legal power, control, or regulatory oversight over a given entity or activity.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d3128348190836158467e9cfbe2 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:19 p.m.