Triple
T8495501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IR8 |
E201088
|
entity |
| Predicate | geographicAdoption |
P55272
|
FINISHED |
| Object | widely adopted in India |
—
|
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: widely adopted in India | Statement: [IR8, geographicAdoption, widely adopted in India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicAdoption Context triple: [IR8, geographicAdoption, widely adopted in India]
-
A.
globalAdoption
Indicates that something has been accepted, implemented, or used worldwide across many or all regions or populations.
-
B.
geographicContext
Indicates that one entity is situated within, associated with, or characterized by the geographic setting or region defined by another entity.
-
C.
countryOrRegionOfPrevalence
chosen
Indicates the country or geographic region where something (such as a condition, practice, or phenomenon) is most commonly found or occurs most frequently.
-
D.
geographicDistribution
Indicates the spatial range or area over which something occurs, exists, or is found.
-
E.
marketAdoption
Indicates the extent to which a product, service, or innovation has been accepted and used by its target market or customer base.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe57dbe488190af5f06faf862cd5d |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:13 p.m.