Triple
T1668834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Power Query |
E36075
|
entity |
| Predicate | uses |
P98
|
FINISHED |
| Object | M language |
E188108
|
NE 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: M language | Statement: [Power Query, uses, M language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M language Context triple: [Power Query, uses, M language]
-
A.
M language
chosen
M language is a functional, case-sensitive data mashup and transformation language used primarily in Microsoft Power Query for importing, shaping, and combining data from diverse sources.
-
B.
Mono language
Mono language is a Native American Uto-Aztecan language traditionally spoken by the Mono people of eastern California.
-
C.
Microsoft Intermediate Language
Microsoft Intermediate Language is the low-level, platform-independent bytecode used by the .NET Framework’s Common Language Runtime as the compilation target for .NET languages before just-in-time compilation to native machine code.
-
D.
F#
F# is a functional-first, multi-paradigm programming language for the .NET platform, known for its strong type system and concise, expressive syntax.
-
E.
M-Code
M-Code is an advanced, encrypted military GPS signal designed to provide more secure and jam-resistant positioning and navigation for authorized users.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a8861286808190939afff3ce8ee31e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90adf3d3c81909233e574e79b82a2 |
completed | March 5, 2026, 4:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad71b0cde08190a210cf387459e9ad |
completed | March 8, 2026, 12:55 p.m. |
Created at: March 4, 2026, 7:29 p.m.