Triple
T6233569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McCreary County v. ACLU of Kentucky |
E139414
|
entity |
| Predicate | locationOfDisplays |
P53354
|
FINISHED |
| Object | Kentucky county courthouses |
—
|
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: Kentucky county courthouses | Statement: [McCreary County v. ACLU of Kentucky, locationOfDisplays, Kentucky county courthouses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfDisplays Context triple: [McCreary County v. ACLU of Kentucky, locationOfDisplays, Kentucky county courthouses]
-
A.
displays
Indicates that one entity visually presents or shows another entity’s content or information.
-
B.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
-
C.
displaysFeature
Indicates that one entity presents, shows, or makes visible a particular feature or characteristic of another entity.
-
D.
exhibitLocation
chosen
Indicates the place or venue where something is displayed, presented, or put on exhibit.
-
E.
plateLocation
Indicates the spatial position or placement of a plate relative to a reference location or object.
- 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_69c008b0e7ac8190808a59573ee646f3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062efa25c8190a54f5a6f5b5ad24f |
completed | March 22, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69c05601de6481909d0880048fd7b49a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:22 p.m.