Triple
T12323623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AWS Amplify |
E293777
|
entity |
| Predicate | supports |
P516
|
FINISHED |
| Object | Flutter |
E131750
|
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: Flutter | Statement: [AWS Amplify, supports, Flutter]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Flutter Context triple: [AWS Amplify, supports, Flutter]
-
A.
Flutter
chosen
Flutter is an open-source UI toolkit by Google for building natively compiled, cross-platform applications from a single Dart codebase.
-
B.
Flutter Engine
Flutter Engine is the portable, high-performance runtime at the core of Flutter that renders UI, executes Dart code, and interfaces with platform-specific services across different operating systems.
-
C.
Dart
Dart is a client-optimized, object-oriented programming language developed by Google, primarily used for building web and cross-platform mobile applications (notably with the Flutter framework).
-
D.
Flutter DevTools
Flutter DevTools is a suite of performance and debugging tools for profiling, inspecting, and optimizing Flutter applications.
-
E.
Flutter CLI
Flutter CLI is the command-line interface tool used to create, build, run, and manage Flutter applications across different platforms.
- 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_69d6ab6ae0dc8190b1522a9c1c55c114 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f4d7dac81909ff10e64e229ef33 |
completed | April 10, 2026, 6:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f61e8d27288190bdf32acd600141db |
completed | May 2, 2026, 3:55 p.m. |
Created at: April 8, 2026, 9:53 p.m.