Triple
T32508471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Jefferson City |
E830864
|
entity |
| Predicate | coversCountiesIn |
P5971
|
FINISHED |
| Object | central Missouri |
—
|
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: central Missouri | Statement: [Diocese of Jefferson City, coversCountiesIn, central Missouri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversCountiesIn Context triple: [Diocese of Jefferson City, coversCountiesIn, central Missouri]
-
A.
hasNumberOfCounties
Indicates the relationship that specifies how many counties are associated with or contained within a given entity.
-
B.
eachCountyHas
Indicates that for every county in a given set or context, there exists at least one associated item, attribute, or entity satisfying a specified condition.
-
C.
includesCounty
chosen
Indicates that a larger geographic or administrative region contains or encompasses a specific county within its boundaries.
-
D.
inCounty
Indicates that one entity is geographically or administratively located within the boundaries of a specified county.
-
E.
representsCountyIn
Indicates that an entity serves as an official representative or acts on behalf of a specific county.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 1, 2026, 1 a.m.