Triple
T34531338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All-State |
E886543
|
entity |
| Predicate | geographicGranularity |
P109501
|
FINISHED |
| Object | individual U.S. states |
—
|
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: individual U.S. states | Statement: [All-State, geographicGranularity, individual U.S. states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicGranularity Context triple: [All-State, geographicGranularity, individual U.S. states]
-
A.
granularityLevel
chosen
Indicates the degree of detail or resolution at which something is specified, measured, or analyzed within a given context.
-
B.
geographicCriterion
Indicates that the relationship or selection is determined based on geographic factors, such as location, region, or spatial boundaries.
-
C.
geographicCoverageType
Indicates the type or nature of the geographic area that something covers or applies to.
-
D.
scalingGranularity
Indicates the level of detail or resolution at which a quantity, process, or system is adjusted or scaled.
-
E.
outputGranularity
Indicates the level of detail or resolution at which results or data are produced or reported.
- 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 1, 2026, 2:02 a.m.