Triple
T31844580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salem Limestone |
E812901
|
entity |
| Predicate | majorQuarryDistrict |
P79110
|
FINISHED |
| Object | Lawrence County, Indiana |
—
|
NE NERFINISHED |
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: Lawrence County, Indiana | Statement: [Salem Limestone, majorQuarryDistrict, Lawrence County, Indiana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorQuarryDistrict Context triple: [Salem Limestone, majorQuarryDistrict, Lawrence County, Indiana]
-
A.
quarryRegion
chosen
Indicates that a specified region is the location where quarrying or extraction activities take place.
-
B.
majorDistrict
Indicates that one administrative district is the primary or most significant district associated with another entity or area.
-
C.
isMainDistrictOf
Indicates that a district serves as the primary or central administrative district of a specified larger area or jurisdiction.
-
D.
majorCityInDistrict
Indicates that a city serves as a major or principal urban center within a specified district.
-
E.
hadDistrict
Indicates that an entity previously possessed, was associated with, or was administered by a particular district.
- 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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69feabcda59481908f2bc13b46fcced1 |
completed | May 9, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69feaabd63f88190b30dcf6dd2ea39d1 |
completed | May 9, 2026, 3:32 a.m. |
Created at: April 30, 2026, 11:50 p.m.