Triple
T12238246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleveland County |
E291656
|
entity |
| Predicate | hasJurisdiction |
P285
|
FINISHED |
| Object | Noble |
E970893
|
NE 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: Noble | Statement: [Cleveland County, hasJurisdiction, Noble]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Noble Context triple: [Cleveland County, hasJurisdiction, Noble]
-
A.
Noble
Noble is a surname of English origin historically associated with social rank and often borne by families of distinction.
-
B.
Noble
chosen
Noble is a small city in Cleveland County, Oklahoma, known for its close-knit community and proximity to the Oklahoma City metropolitan area.
-
C.
Noble
Noble is an unincorporated community and residential area within Abington Township in Montgomery County, Pennsylvania.
-
D.
Regal
Regal is a major American movie theater chain known for operating multiplex cinemas across the United States.
-
E.
Nobilior
Nobilior is the cognomen of the Roman statesman and general Marcus Fulvius Nobilior, noted for his military campaigns and cultural patronage during the Roman Republic.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ab668acc8190963ba424049d6aee |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91cb45340819093365f8efdf85f75 |
completed | April 10, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f61e5ff68c81909d2796b24dd055f4 |
completed | May 2, 2026, 3:55 p.m. |
Created at: April 8, 2026, 9:51 p.m.