Triple
T27612873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Search API |
E700369
|
entity |
| Predicate | exposesEndpoint |
P148404
|
FINISHED |
| Object | /search/qnas |
—
|
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: /search/qnas | Statement: [Microsoft Search API, exposesEndpoint, /search/qnas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exposesEndpoint Context triple: [Microsoft Search API, exposesEndpoint, /search/qnas]
-
A.
endpointInclusion
Indicates that one endpoint is contained within or is part of another endpoint or endpoint set.
-
B.
typicalEndpoint
chosen
Indicates that something represents the standard or commonly used endpoint associated with another entity or process.
-
C.
exposesTo
Indicates that one entity subjects another entity to contact with or influence from something, typically involving risk, effect, or experience.
-
D.
exposedAs
Indicates that one entity reveals or publicly identifies another entity as having a hidden, false, or previously concealed role, identity, or nature.
-
E.
endPoint
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
- 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_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 2:11 p.m.