Triple
T22864909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expo |
E567024
|
entity |
| Predicate | provides |
P490
|
FINISHED |
| Object | Expo SDK |
—
|
NE NERFINISHED |
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: Expo SDK | Statement: [Expo, provides, Expo SDK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Expo SDK Context triple: [Expo, provides, Expo SDK]
-
A.
Expo Application Services
Expo Application Services is a suite of cloud-based tools and infrastructure that streamlines building, deploying, and managing React Native apps created with the Expo platform.
-
B.
Expo framework
chosen
Expo framework is an open-source toolchain and platform for building, deploying, and iterating on React Native applications with minimal native configuration.
-
C.
Expo CLI
Expo CLI is a command-line tool used to create, develop, build, and manage React Native apps within the Expo ecosystem.
-
D.
Expo Go
Expo Go is a mobile app that lets developers instantly run and preview React Native projects on their devices without building native binaries.
-
E.
React Native
React Native is a JavaScript framework developed by Meta for building native mobile applications for iOS and Android using React components.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17effd93081909f2c9a8857a8728b |
completed | April 29, 2026, 3:46 a.m. |
Created at: April 17, 2026, 3:38 p.m.