Triple
T37706880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SharePoint Store |
E939219
|
entity |
| Predicate | goverenedBy |
P98499
|
FINISHED |
| Object | SharePoint app catalog settings |
—
|
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: SharePoint app catalog settings | Statement: [SharePoint Store, goverenedBy, SharePoint app catalog settings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goverenedBy Context triple: [SharePoint Store, goverenedBy, SharePoint app catalog settings]
-
A.
areGovernedBy
chosen
Indicates that one or more entities are under the authority, control, or administration of a governing body or ruler.
-
B.
governedFrom
Indicates that an entity exercises governing authority or administrative control over another entity from a specific location or seat of power.
-
C.
governedFor
Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest of, another entity.
-
D.
governedIn
Indicates that one entity exercised governing authority or administrative control within a specified place or jurisdiction.
-
E.
governedWith
Indicates that two or more entities share or participate together in the act or process of governing.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.