Triple
T32416384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AppLifecycle namespace |
E828340
|
entity |
| Predicate | containsAPI |
P31856
|
FINISHED |
| Object | activation APIs |
—
|
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: activation APIs | Statement: [AppLifecycle namespace, containsAPI, activation APIs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsAPI Context triple: [AppLifecycle namespace, containsAPI, activation APIs]
-
A.
includesAPI
Indicates that one entity provides or contains an application programming interface (API) that can be used by another entity.
-
B.
hasAPIs
chosen
Indicates that one entity provides or exposes application programming interfaces (APIs) that can be used or accessed by another entity.
-
C.
hasAPIConcept
Indicates that one entity includes, defines, or is associated with a particular API-related concept.
-
D.
supportsJavaScriptAPIs
Indicates that one entity provides or is compatible with JavaScript-based application programming interfaces for use by another entity.
-
E.
componentIncluded
Indicates that one entity is a constituent part or subcomponent that is contained within or included in another entity.
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ffc89596d08190b97bd60b45c7f9c0 |
completed | May 9, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69ffc81ba5dc8190ae94d44e2284948f |
completed | May 9, 2026, 11:49 p.m. |
Created at: May 1, 2026, 12:54 a.m.