Triple
T4741638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marion County, Kentucky |
E105256
|
entity |
| Predicate | isInlandCounty |
P45084
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Marion County, Kentucky, isInlandCounty, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInlandCounty Context triple: [Marion County, Kentucky, isInlandCounty, true]
-
A.
isInLandlockedCounty
chosen
Indicates that an entity is located within a county that has no direct access to the ocean or sea.
-
B.
isInlandTown
Indicates that a town is located away from the coast, without direct access to the sea or ocean.
-
C.
isInlandCity
Indicates that a city is located away from the coast, without direct access to the sea or ocean.
-
D.
isInlandFrom
Indicates that one place lies away from the coast, further toward the interior of the land, relative to another place.
-
E.
isInCountySubdivision
Indicates that one entity (typically a place or address) is located within the boundaries of a specific county subdivision.
- 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64a7153881909eac451fc7566d25 |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:19 p.m.