Triple
T4762769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IN-MH |
E105734
|
entity |
| Predicate | codeStructureExample |
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: [IN-MH, codeStructureExample, IN-MH]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeStructureExample Context triple: [IN-MH, codeStructureExample, IN-MH]
-
A.
programStructure
Indicates how components, modules, or elements are organized and related within a program or system.
-
B.
codeExample
chosen
Indicates that one entity provides a snippet or sample of source code that illustrates how to use, implement, or demonstrate another entity.
-
C.
codeSection
Indicates a specific segment or subsection within a larger body of code that is distinguished for reference, organization, or analysis.
-
D.
encodingStructure
Indicates the structural scheme or format used to encode information or data.
-
E.
displayStructure
Indicates that one entity presents or reveals the internal organization, layout, or arrangement of another 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd686ef1b08190ad60375592c9d6c0 |
completed | March 20, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69bd622807f881908e4bcb14f7731bac |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.