Triple
T27612910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Search API |
E700369
|
entity |
| Predicate | hasPreviewFeatures |
P79856
|
FINISHED |
| Object | beta endpoint in Microsoft Graph |
—
|
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: beta endpoint in Microsoft Graph | Statement: [Microsoft Search API, hasPreviewFeatures, beta endpoint in Microsoft Graph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPreviewFeatures Context triple: [Microsoft Search API, hasPreviewFeatures, beta endpoint in Microsoft Graph]
-
A.
developerPreviewFor
chosen
Indicates a relationship where one entity serves as a developer-focused preview or early-access version of another entity.
-
B.
hasFeatureStatus
Indicates that an entity possesses a particular feature along with its current state or condition.
-
C.
hasFeature
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
D.
plannedFeature
Indicates that a particular feature is intended or scheduled to be developed or implemented in the future.
-
E.
hasSideFeature
Indicates that an entity possesses a specific secondary or auxiliary feature on its side or lateral aspect.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: April 27, 2026, 2:11 p.m.