Triple
T22649508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expo |
E559055
|
entity |
| Predicate | supportsDevelopmentMode |
P114279
|
FINISHED |
| Object | hot reloading |
—
|
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: hot reloading | Statement: [Expo, supportsDevelopmentMode, hot reloading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDevelopmentMode Context triple: [Expo, supportsDevelopmentMode, hot reloading]
-
A.
supportsDevelopmentProcess
chosen
Indicates that one entity provides resources, tools, or assistance that facilitate or enhance another entity’s development process.
-
B.
supportsDeveloper
Indicates that one entity provides assistance, resources, or advocacy to help a developer perform their work or achieve their goals.
-
C.
supportsDevelopmentLanguage
Indicates that one entity provides compatibility with, tools for, or the ability to use a particular programming or development language.
-
D.
hasDevelopmentType
Indicates the type or category of development associated with an entity, such as the nature, form, or stage of its development.
-
E.
hasDevelopmentSystem
Indicates that one entity possesses, uses, or is associated with a particular system, platform, or environment used for development activities.
- 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1703a84b081909a683f8c850dcbf9 |
completed | April 29, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:05 p.m.