Triple
T31397699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1980 United States census |
E800903
|
entity |
| Predicate | summaryDataAvailableFrom |
P76522
|
FINISHED |
| Object | National Historical Geographic Information System |
—
|
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: National Historical Geographic Information System | Statement: [1980 United States census, summaryDataAvailableFrom, National Historical Geographic Information System]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summaryDataAvailableFrom Context triple: [1980 United States census, summaryDataAvailableFrom, National Historical Geographic Information System]
-
A.
dataAvailableFrom
chosen
Indicates that a specified source or provider offers access to certain data starting from a particular point or under certain conditions.
-
B.
dataAvailableAs
Indicates that specific data can be accessed or obtained in a particular form, format, or representation.
-
C.
dataReleaseDate
Indicates the date on which a particular dataset or piece of data is officially made available or published.
-
D.
supportsDataFrom
Indicates that one entity provides, validates, or underpins the data used or referenced by another entity.
-
E.
requiresDataAvailability
Indicates that one entity’s operation, validity, or execution is contingent on the presence, accessibility, or readiness of specific 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:19 p.m.