Triple
T15694920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IN-GJ |
E380433
|
entity |
| Predicate | associatedCountryCodeISO3166-1 |
P42506
|
FINISHED |
| Object | IN |
—
|
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: IN | Statement: [IN-GJ, associatedCountryCodeISO3166-1, IN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCountryCodeISO3166-1 Context triple: [IN-GJ, associatedCountryCodeISO3166-1, IN]
-
A.
associatedCountryCode
chosen
Indicates that there is a relationship linking something to the country identified by the given country code.
-
B.
associatedCountry
Indicates that there is a relevant connection or linkage between an entity and a specific country, such as origin, operation, or affiliation.
-
C.
associatedCountryMostProminently
Indicates the country with which an entity is most strongly or prominently associated, relative to any other countries it may be linked to.
-
D.
associatedCountryCodeSystem
Indicates that there is a relationship between an entity and the country code system it is associated with or governed by.
-
E.
bearerCountry
Indicates the country that serves as the issuer or origin nation associated with a given bearer (such as a document, instrument, or entity).
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0051d639481909a10614e8f83e659 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:44 a.m.