Triple
T35853858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Census of Kentucky counties |
E1036441
|
entity |
| Predicate | dataAccessPortal |
P14669
|
FINISHED |
| Object | data.census.gov |
—
|
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: data.census.gov | Statement: [U.S. Census of Kentucky counties, dataAccessPortal, data.census.gov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataAccessPortal Context triple: [U.S. Census of Kentucky counties, dataAccessPortal, data.census.gov]
-
A.
dataPortal
chosen
Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
-
B.
dataAccessibleTo
Indicates that certain data can be reached, retrieved, or used by a specified entity or system.
-
C.
dataAccessModel
Indicates the framework or scheme that governs how data can be accessed, including who can retrieve it, under what conditions, and through which mechanisms.
-
D.
dataContext
Indicates the situational or environmental conditions under which data is produced, interpreted, or used, such as source, scope, assumptions, and relevant constraints.
-
E.
dataAccessTechnology
Indicates the technology or method used to access, retrieve, or interact with data.
- 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3883d48190b05e3d2da7a017ae |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.