Triple
T3938796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America/Managua |
E90980
|
entity |
| Predicate | regionCategory |
P26631
|
FINISHED |
| Object | America time zones |
—
|
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: America time zones | Statement: [America/Managua, regionCategory, America time zones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionCategory Context triple: [America/Managua, regionCategory, America time zones]
-
A.
regionType
Indicates the classification or category of a region, specifying what kind of region it is (e.g., administrative, geographic, or functional).
-
B.
regionClassification
chosen
Indicates how a given area or location is categorized into a specific region based on defined criteria or boundaries.
-
C.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing another entity.
-
D.
regionOfCity
Indicates that a specified area or district is a constituent part or subdivision of a particular city.
-
E.
countryIncludes
Indicates that a country geographically or administratively contains or encompasses a specified region, territory, or subdivision.
- 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_69aed95f26e0819094b0e71974543a19 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeedfb12b88190a6ca6574b1aadb6e |
completed | March 9, 2026, 3:57 p.m. |
| PD | Predicate disambiguation | batch_69aee7625ad4819097e4e8a168c19274 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:24 p.m.