Triple
T4615954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 3166-2:IN |
E100868
|
entity |
| Predicate | exampleCode |
P30248
|
FINISHED |
| Object | IN-MH |
—
|
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-MH | Statement: [ISO 3166-2:IN, exampleCode, IN-MH]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exampleCode Context triple: [ISO 3166-2:IN, exampleCode, IN-MH]
-
A.
codeExample
chosen
Indicates that one entity provides a snippet or sample of source code that illustrates how to use, implement, or demonstrate another entity.
-
B.
code
Indicates that an entity writes, develops, or produces computer software or source code.
-
C.
scriptCode
Indicates that an entity is associated with a particular writing system or script, identified by a standardized script code.
-
D.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
E.
codeSection
Indicates a specific segment or subsection within a larger body of code that is distinguished for reference, organization, or analysis.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59df3c3c8190be5db000f831d322 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.