Triple
T22649552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expo toolchain |
E559056
|
entity |
| Predicate | supportsConfigFormat |
P105434
|
FINISHED |
| Object | app.json |
—
|
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: app.json | Statement: [Expo toolchain, supportsConfigFormat, app.json]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsConfigFormat Context triple: [Expo toolchain, supportsConfigFormat, app.json]
-
A.
hasConfigurationFormat
chosen
Indicates that an entity uses or is associated with a specific configuration format for its settings or parameters.
-
B.
supportsTextFormat
Indicates that one entity is capable of handling, rendering, or otherwise working with a specified text format.
-
C.
supportsBackupFormat
Indicates that one entity is capable of handling, storing, or operating with another entity as a backup data format.
-
D.
supportsDebugFormats
Indicates that one entity provides or is compatible with debugging data or formats used by another entity.
-
E.
supportsConfigInheritance
Indicates that one configuration can derive from and reuse settings defined in another configuration.
- 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.